End Stage Report
Tailoring
The End Stage Reports are a combination of information generated at the end of the iterations and releases inside the Stage, and therefore, they might be prepared incrementally during the stage.
Like the Review meetings at the end of the Scrum Sprints, it's also possible to have review meetings for releases and stages. In that case, the End Stage Report would be part of the information communicated at the meeting.
It's helpful to have the report focused on the business value created during the stage, and adaptations that happened after each iteration.
Reminder: Each management stage can contain one or more releases, and each release can contain one or more iterations. So, based on the tailoring done in the project, you can choose the simplest form in which each management stage is a Sprint (assuming you're using Scrum in the delivery level), and therefore the End Stage Report would be the same as the information communicated at the Sprint Review meeting. On the other hand, you can have three separate levels of stages, releases, and Sprints, if the project is complex; in this case, the End Stage Report should be a combination of the Sprint Review meetings' information and more.
Process Model
Legend:
- 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)
Notes:
- 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.
External Links
- End Stage Report at PRINCE2 wiki
