1. OGC’s
PRINCE2™

2. 7 PRINCE 2 principles
P2 projects have a continued business justification.
P2 projects have defined and agreed roles and responsibilities.
P2 projects are managed (planned, monitored and controlled) on a stage by stage basis.
P2 projects have defined tolerances to establish limits of delegated authority (management by exception).
P2 projects focus on the definition and delivery of products.
P2 projects are tailored to suit the projects environment, size, complexity, importance, capability and risk.
P2 projects learn from previous experience (lessons).

3. 7 PRINCE 2 Themes Business Case (Why?) Organisation (Who?
Quality (What?)
Plans (How, How much, When?)
Risk (What if?)
Change (What’s the impact)
Progress (Where are we now? Where are we going? Should we carry on?)

4. 7 PRINCE Processes Directing Project Planning Controls
Quality
Mgmt of Risk
Organisation
Business Case
7 PRINCE Processes
Controls
Starting up a Project
Directing Project
Plans
Quality
Mgmt of Risk
Business Case
Controls
Configuration Mgmt
Change Control
Initiating a Project
Planning
Controlling a Stage
Controls
Change Control
Configuration Mgmt
Business Case
Mgmt of Risk Quality
Quality review
Change control
Change Control
Quality
Controls
Plans Mgmt of Risk
Managing Product Delivery
Plans
Quality
Business Case
Mgmt of Risk
Controls Organisation
Managing Stage Boundaries
Closing a Project
Controls
Configuration Mgmt
Business Case
Mgmt of Risk
Change Control
Product-based planning
Key = Techniques = Component =Process
Pink
Grey
Clear

5. PRINCE2 Documentation
Business case
Project Mandate
Project Brief
Project Initiation Document (PID)
Project Plan/Stage Plan
Product checklist
Risk logs/Issue logs
Quality logs
Request for Change
Work Package
Project Quality Plan
Exception Plan
Post-Project Review Plan

6. Project Initiation Document
Introduction, explaining the context of the project, and how we have arrived at the current position of requiring a project:
Context
Objectives
Authority
Project Definition, explaining what the project needs to achieve:
Key deliverables
Constraints
Assumptions
Exclusions
Interfaces
External dependencies
Tolerance
Benefits
Costs

7. PID content continued Approach Project Plan Contingency Plan
Communication and Stakeholder plans
Project Organisation Structure
Reporting Cycle
Risk Management
Quality Management

8. Benefits of PRINCE2™
The method is widely recognized and understood, and therefore provides a common vocabulary for all project participants - promoting effective communication.
T he method also provides for the explicit recognition of project responsibilities - so that participants understand each other's roles and needs.
There is a defined structure for accountability, delegation, authority and communication.

9. Any Questions?