Project Initiation Documentation
It's important to have a proper level of detail in the Project Initiation Documentation, otherwise:
- If it's too detailed, there won't be enough room for self-organization and adaptation in the delivery level and it would block adaptation
- If it's too high-level, not enough governance would be created in the project, and there would be no benefits from using PRINCE2
PRINCE2 Agile provides the following recommendations for the Project Initiation Documentation:
- It would be more high-level to allow for self-organization and adaptation in the delivery layer.
- It might be simpler and shorter than usual.
- It might be informal.
- It might be presented on Information Radiators.
- It might be created in a facilitated workshop.
- It also includes the result of The Agilometer assessment.
- The project-level tolerances for time and cost might be set to zero to focus only on managing the quantity of what is delivered (see note below).
Note: the term "tolerance" is used in its common language form in PRINCE2 Agile, which is not compatible with PRINCE2's definition of tolerance, whichis used with Manage by Exception Principle to show who should decide on corrective actions. Setting zero tolerances is not a way of fixing a target, while it's incorrectly described so in PRINCE2 Agile. More on this in the Targets article.
- 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.
- Initiating a Project Process
- p2:Project Initiation Documentation Theme in PRINCE2 wiki