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

Project Portal
| See Also Help |
| ### Next Steps Verify a Build Accept Build |
| Activity: Start a Build
|  |  | Build a Product |  |
### Overview Start a build whenever there is a need to integrate changes or ensure build consistency. Creating a build helps to synchronize changes and creates a platform on which all developers can work. If the build process gets too slow, rework dependencies to make it faster. # Entry Criteria When: New changes are ready to be integrated into the build. Dependencies: The build is setup and the need for a build is recognized. # Sub-Activities
1 | Keep Dependencies Low | Look for opportunities to cut down the build time by reworking dependencies. Restructure components as necessary to ensure build times stay reasonable. Update any dependency changes resulting from new changes.
2 | Begin Build | When changes are ready to be integrated, start a build. Only create a clean build when absolutely necessary. A clean build occurs during the nightly build. If the build will not run unless a clean build is done, check the dependencies to ensure that the build is running optimally. Coordinate with the other developers to ensure that they are not in the process of checking in development tasks. Start a build to allow others to use changes. Consider the need to run iteration tests based on the time constraints for the build.
# Exit Criteria
| The build is started.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |