Controlling a Stage
It should be noted that PRINCE2 Agile stages, like PRINCE2 stages, are set based on the management perspective rather than delivery perspective used in releases and increments. That's why stages are not considered the same as any of those concepts.
A PRINCE2 Agile stage contains one or more releases, and each release contains one or more iterations (Sprints in Scrum).
Based on this arrangement, the Controlling a Stage process won't have much differences with the original process.
- Progress information is more informal and pull-based (e.g. Information Radiators), or in the Review Meetings
- Controls are simpler, and usually based on simple calculations on the backlogs
- The delivery level has relatively more authority in the Manage by Exception Principle
- Many issues are raised from Daily Standups
Each Work Package would describe multiple releases and iterations, and would be broken down and elaborated into release plans and iteration plans based on the Agile framework in use at the delivery level.
- 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.
- Controlling a Stage Process at PRINCE2 wiki