|
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
 |
|
 |
- Incremental approach
Large and complex programs are organized in incremental builds where each has a greater functionality than the last. Each increment contain all five phases (Inception, Elaboration, Construction, Transition and Evolution)
This allows a shorter time-to-market, because the first increment will already facilitate some functionality before the entire program is finished.
Another important consequence is that the increments are more manageable and that experience from one build can productively be used in future increments. This tackles a problem that often occurred in older methodologies (waterfall model, RAD Time box model etc.).
Click here to view the model
- Iterative approach
Within each phase an iterative approach is used. This means that by repeating an activity for several times a more qualitative result will be produced. This controlled iteration is performed in close collaboration with the customer and allows comments and intermediate proposals.
This is applied to make sure that the essential communication with the client is a fixed part of the methodology. In the inception phase e.g. it guarantees that adequate and stable requirements are constructed.
Click here to view the model
- Cross-phase communication
In order to guarantee a successful end product, close collaboration is established at phase transitions. This means that at the end of the inception phase, persons involved in the elaboration phase will already participate. When the elaboration phase starts, the roles that performed the inception will still assist to initiate that next phase.
Click here to view the model
