Managing a Stage Boundary
The Managing a Stage Boundary is used in the following two boundaries:
- Reaching the end of the stage
- Having an exception
In both cases, the following main activities will be done:
- The justification of the project should be inspected, especially based on the business value created in the previous stages. A similar investigation should happen after each release and iteration, but the one at the stage boundary should be more serious. Remember that each stage includes one or more releases, and each release contains one or more iterations (Sprints in Scrum).
- The next stage, or the remaining of the excepted stage should be Planned, which also includes a high-level plan for the next releases and iterations.
- As a part of planning the next stage, the use of Agile in the previous stages should be investigated, and major improvements planned.
Managing a Stage Boundary should be regarded as another opportunity for adaptation:
- Iterations: small adaptations, mainly decided by the delivery team
- Releases: intermediate-level adaptation, mainly decided by the Project Manager
- Boundaries: high-level adaptation, mainly decided by the Project Board
For example, if a change in the market makes a big difference in the project, there would be a large deviation in project targets because of the changes in business values, which in turn, causes an exception, and results in a high-level adaptation (change) decided by the Project Board.
- SU: Starting up a Project Process
- IP: Initiating a Project Process
- SB: Managing a Stage Boundary Process
- CP: Closing a Project Process
- (DP): Directing a Project Process (note that not all activities in this process are shown in this diagram)
- The above image assumes that Scrum is used in the delivery level, which is not necessary.
- The number of stages, releases, and Sprints are just examples, as well as the exception in the third stage.
- The diagram is schematic and many details are not shown.
- Managing a Stage Boundary Process at PRINCE2 wiki