16.2 Tailoring guidance for the PRINCE2 processes
Figure 16.2 shows the seven PRINCE2 processes and the PRINCE2 management products (see Table 16.1 for a key to the abbreviations). More details of how sprints and flow-based timeboxes are incorporated are shown in the inset, which has been expanded in Figure 16.3.
The numbers in Figures 16.2 and 16.3 refer to the PRINCE2 management products as identified in the PRINCE2 manual and shown in Table 16.2 (see Chapter 23 and Appendix A for further information about the products).
|Abbreviation||PRINCE2 process||Key agile artefacts and events that may exist within the process|
Directing a Project
Starting up a Project
Vision, product roadmap
Initiating a Project
Controlling a Stage
Release(s), release backlog, release retrospective
Managing Product Delivery
Sprint(s), sprint backlog, sprint review and retrospective
Managing a Stage Boundary
As for CS
Managing a Stage Boundary (when an exception has occurred)
As for CS
Closing a Project
Table 16.1 Key to abbreviations in Figures 16.2 to 16.4
|Baseline management products, shown in red||Records, shown in black||Reports, shown in blue|
1 Benefits review plan
2 Business case
4 Communication management strategy
6 Configuration management strategy
16 Plan (covers project, stage and, optionally, team plans)
17 Product description
19 Project brief
20 Project initiation documentation (PID)
21 Project product description
22 Quality management strategy
24 Risk management strategy
26 Work package
5 Configuration item records
7 Daily log
12 Issue register
14 Lessons log
23 Quality register
25 Risk register
3 Checkpoint report
8 End project report
9 End stage report
10 Exception report
11 Highlight report
13 Issue report
15 Lessons report
18 Product status account
Table 16.2 Key to the PRINCE2 management products
Note that where the number 16 appears in brackets in Figures 16.2 and 16.3, it denotes more than one type of plan.
Figure 16.3 shows how releases and low-level timeboxes (i.e. as sprints or flow-based) may appear inside a PRINCE2 management stage. The figure assumes a common agile situation where a product backlog is used to create a series of releases, and each release in turn creates a series of sprints (e.g. when using Scrum) or is run as one timebox using a flow-based approach (e.g. when using Kanban).
Although this represents a common approach there are many other equally valid situations (see Figure 16.4). Examples of such situations might be:
- Releases and release backlogs are not used because sprints and sprint backlogs are all that are required. In this case a sprint may result in a release of features into operational use, or a release of features into a staging area or an interim deliverable which is of use to the project.
- Releases happen so frequently that they are not treated as a type of timebox or in need of a release backlog. In this case a release may happen at the end of each timebox or on more than one occasion during the timebox.
- A management stage could relate to just one release.