Be Structured can be tailored to specific circumstances; this makes alternative flows possible through the activities. The actual flow strongly depends on the project’s context: sales process, risks, changes, incremental releases, experience of team as well as partner and/or client preferences.
A typical flow is shown in the figure below.
The first milestone is the go/no-go decision at the end of de Discover phase. The project ends with a no-go and will continue with a go. In that case a bid is done to the customer. The customer can accept or reject this offer and lengthy negotiations may take place, but these steps are not a part of this methodology.
When we proceed the next milestone is when the core application is ready for demonstration and acceptance. This application demonstrates a blueprint of the behavior repertoire of the final solution as well as its critical qualities. As such this is a major milestone for acceptance. When there is an agreement all remaining functionality is realized based on this blueprint.
The next milestone is achieved when the solution is mature enough for first production. Criteria for this moment are decided upon in a very early stage of course. After formal acceptance the solution is put into its first production and is ready for use. Acceptance, system transitions and required organizational transformations are prepared in advance of course.
Now a number of improvement cycles will follow. Some of them might have been planned in advance while others emerge during the solution’s life-cycle.