An accepted build indicates minimum quality standards are successfully met and the build is ready for further work. To accept a build, make sure compilation and verification tests cover all functionality and run successfully.
Entry Criteria
When:
Build has been verified.
Dependencies:
Build completed, build report reviewed: The build report contains no critical errors. It may contain some warnings.
Sub-Activities
1
Manage Build Tests
Remove or add sections of the build verification tests that measure the functionality necessary to deem the build self-test and not self-toast.
Add tests to the build verification test folder and check in the tests.
Monitor the iteration tests to understand progress within the iteration.
Post iteration test results.
2
Monitor Build Health
Monitor the health of the build by examining the build details report.
Fix builds that do not compile or pass build verification tests. Make healthy builds available to the business analysts for exploratory testing.
Look for an increase in build time. If the build time becomes too long, rework dependencies.
Make sure notifications are sent and the list of interested parties is up-to-date.
Program Management
