Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| Accept a Build ( 3 : PI : 3 : 3.1 ) ( 2 : CM : 1 : 1.3 ) Build Engineer
Activity: Accept a Build
Build Engineer
|  |  |  | Build |  |  |  | Stabilize |  |
|  | Participating Roles Responsible: Build Engineer
### Overview 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. An accepted build represents a reproducible baseline of the product code. # Entry Criteria Build completed, build report reviewed The build report contains no critical errors. It may contain some warnings. When: Build has been verified. # 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. This can be done by marking the build quality of the build in the Team Build Browser. 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.
# Exit Criteria
| The build runs optimally.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |