Project Mandate

Initiation notification
Project authorization
notification
Project Board
request for advice
Corporate advice
and decisions
Closure notification
PRINCE2 Process model version 1.03
(Based upon the manual Managing Successful Projects with PRINCE2, 2009 edition)
PRINCE2 is a Registered Trade Mark of the Office of Government
Commerce in the United Kingdom and other countries. Based upon
OGC (PRINCE2) material. Reproduced under licence from OGC
Request to
initiate a project
Authority to
initiate a project
8,9
Request to
deliver a project
11, 13, Lessons Log
Request to approve
next Stage Plan
Request to approve
Exception Plan
1,3,8,10,11,12
1,8,10,11,12,13
DP
Directing a Project
Authorize
initiation
Authorize a
Stage or
Exception Plan
Stage authorization
Exception Plan
approved
Request for advice
Exception raised
12
13
Project Board advice Premature close
14 Exception Plan
request
Closure
recommendation
Authority to deliver a
Work Package
Completed
Work Package
8
1
Stage boundary
approaching
Project end
approaching
Premature close
New issue
SU
Starting up a Project
Products:
1. Daily Log (CU)
2. Lessons Log (C)
3. PM team role descriptions* (C)
4. PM team structure* (C)
5. (Outline) Business Case (C)
6. Project Product Description (C)
7. Project approach* (C)
8. Project Brief (C)
9. (Initiation) Stage Plan (C)
Appoint the
Executive &
Project Manager
Capture
previous
lessons
Design and
appoint the project
management team
Prepare the
outline
Business Case
Select the
project approach
& assemble the
Project Brief
Plan the
initiation stage
Premature close
IP
Initiating a Project
Products:
1. Risk Management Strategy (C)
2. Risk Register (CU)
3. Configuration Management Strategy (C)
4. Configuration Item Records (CU)
5. Issue Register (CU)
6. Quality Management Strategy (C)
7. Quality Register (C)
8. Communication Management Strategy (C)
9. Project controls* (C)
10. Project Plan (C)
11. Benefits Review Plan (C)
12. (Detailed) Business Case (C)
13. Project Initiation Documentation (C)
14. PM team role descriptions* (U)
15. PM team structure* (U)
Prepare the
Configuration
Management
Strategy
Prepare the
Communication
Management
Strategy
Create the
Project Plan
Products
1. Project Plan (U)
2. Product Status Account (C)
3. Issue Register (U)
4. Additional work estimates* (C)
5. Follow on action
recommendations* (C)
6. Configuration Item Records (U)
7. Benefits Review Plan (U)
8. Acceptance records* (obtain)
9. End Project Report (C)
10. Lessons Report (C)
11. Draft project closure notification*
(prepare)
12. Risk Register (Close)
13. Quality Register (close)
14. Issue Register (close)
15. Daily Log (close)
16. Lessons Log (close)
CP Closing a Project SB
Managing a Stage Boundary
Products:
1. Project Initiation Documentation (U)
2. Configuration Item Records (CU)
3. (Next) Stage Plan (C)
4. Risk Register (U)
5. Issue Register (U)
6. Quality Register (U)
7. Project Plan (U)
8. Benefits Review Plan (U)
9. Business Case (U)
10. End Stage Report (C)
11. Lessons Report (C)
12. Follow-on action recommendations* (C)
13. Exception Plan (C)
Plan the
next stage
Update the
Project Plan
Report
stage end
PRINCE2
training
specialists
For more copies of this wall chart, or for information about
PRINCE2 training, contact Knowledge Train at:
2nd Floor
14 Charterhouse Square
London EC1M 6AX
United Kingdom
+44(0)20-7148-5985 | info@ knowledgetrain.co.uk
www.knowledgetrain.co.uk
KEY
Trigger
8,9
This is a PRINCE2 process. Products which are not PRINCE2
management products are denoted by an asterisk*. The products
used in the process are specified as followed:
(A) - Approved
(C) - Created
(R) - Reviewed
(U) - Updated
This is an activity. Each process comprises a number
of activities.
This is an event or decision that triggers another process or
is used to notify corporate or programme management.
The arrow shows which process is triggered by the event.
These show the products output from one process to another.
CS
Controlling a Stage
Products:
1. Work Package (C)
2. Configuration Item Records (CU)
3. Issue Register (U)
4. Quality Register (U)
5. Risk Register (U)
6. Team Plan (AR)
7. Stage Plan (U)
8. Checkpoint Report (R)
9. Lessons Log (U)
10. Highlight Report (C)
11. Daily Log (U)
12. Issue Report (C)
13. Exception Report (C)
14. Risk* (raise)
15. Issue* (raise)
Escalate
issues and risks
Report highlights
MP
Managing Product Delivery
Products:
1. Team Plan (CU)
2. Quality Register (U)
3. Work Package (AU)
4. Risk* (raise)
5. Issue* (raise)
6. Specialist products* (C)
7. Configuration Item Records (U)
8. Checkpoint Report (C)
9. Approval records* (obtain)
7, 9, 11
Business Case
10
Authorize
the project
Give ad hoc direction
Products:
1. Project Brief (A)
2. Initiation Stage Plan (A)
3. Lessons Log (R)
4. Project Initiation Documentation (A)
5. Benefits Review Plan (A)
6. Specialist Products* (confirm approval)
7. End Stage Report (A)
8. Lessons Report (distribute)
9. Follow on action recommendations* (distribute)
10. Stage Plan (A)
11. Exception Plan (A)
12. Highlight Report (R)
13. Exception Report (R)
14. Issue* (raise)
15. End Project Report (A)
Stage boundary
approaching