The purpose in this phase is to cost-effectively develop a feature-complete product (an operational version of your system) that can be deployed in the user community [KRO03].

The following objectives for the Construction phase help you accomplish that goal:

1. Iteratively develop a complete product that is ready to transition to its user community. Describe the remaining requirements, fill in design details, complete the implementation, and test the software. Release incremental alpha and beta version of the system, and determine if users are ready for the application to be deployed. Further tuning and preparation for final deployment is expected in the Transition Phase.

2. Minimize development costs and achieve some degree of parallelism. Optimize resources and leverage development parallelism between developers or teams of developers by, for example, assigning components that can be developed independently of one another.

Key considerations

Typically, the Construction phase has more iterations (two or more) than the other phases.