On moderate to very large projects, a central control mechanism is needed to ensure that every change is properly considered and coordinated. That’s why on such projects, we establish a Change Control Board. It includes the members from design, development, and test teams. It also sometimes includes the members from the customer team. Its purpose is to ensure that all concerned parties properly consider every baseline change and that every change is authorized before implementation. The CCB is the body that reviews all major change requests, approves them, disapproves them, or defers them for more information. The CCB produces its rapid-development benefit by raising the visibility of feature creep and reducing the number of uncontrolled changes to the product.

• Inspections
• Component Reuseability
• Change Control Board
• Nightly Build and Smoke Test
• Top Ten Risk List