Skip to main content

MSF for CMMI Process Improvement

Go Search
Home
  
MSF for CMMI Process Improvement > Wiki Pages > Activity - Accept a Build  

Activity - Accept a Build

Activity Information

Accept a Build

Description

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.

Roles

ResponsibleBuild Engineer

Attributes

Element Categories[CMMI Report 06] Quality Indicators, [CMMI Level 3] PI SP 3.1, [CMMI Track 3] Build, [CMMI Track 4] Stabilize, [CMMI Level 2] CM SP 1.3, [CMMI Cycle 3] Accepted Build
When

Build has been verified.

Entry Criteria

Build completed, build report reviewed:
The build report contains no critical errors. It may contain some warnings.

Exit Criteria

The build runs optimally:
The build runs optimally.

Is RequiredYes

Steps

  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.

Predecessors

TypeNameDependency Type
Verify a BuildFinish-Start

Last modified at 12/19/2007 10:37 AM  by Administrator