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

Project Portal
| ### Next Steps Test a Scenario Test a Quality of Service Requirement |
| Build a Product Developer
|  | Participating Roles Responsible: Developer
### Overview A team build compiles all new changesets and existing code into a single product. However, when new set of changes is checked into the build, it must be acceptable. The changeset must compile and pass build verification tests. Ensuring the changesets added to the team build do not cause problems is part of accepting a build. Each team build contains a set of build notes that outlines all of the new changes. # Entry Criteria New changesets are ready to be integrated into the team build. The team build is setup and the need for a team build is recognized. # Activities
1 | Start a Build | Keep dependencies low. Begin team build.
2 | Verify a Build | Verify basic functionality. Verify changed functionality. Notify the team of team build acceptance.
3 | Fix a Build | Isolate compile errors. Inspect run-time errors. Inspect team build contents and bill of materials. Inspect installation scripts and executables. Inspect version of dependent modules. Fix and rebuild the team build.
4 | Accept Build | Mange build tests. Monitor build health.
# Exit Criteria
| The team build passes all required build verification tests and the team is notified that the team build is accepted.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |