TSO 2008. Content within this presentation may be subject to change.

PRINCE2: 2009 Project

Progress Update
Warning: this presentation provides a snapshot of the current approach. As the development is based on
continued user consultation the final result may be different. Always check the website for latest information.

www.best-management-practice.com/PRINCE2Register

TSO 2008. Content within this presentation may be subject to change.
Agenda
Progress to Date
Reasons for Change
Differences
PRINCE2 2009 design
Principles
Processes
Key Themes
Project Environment
Management Products
Publications
Managing Successful Projects Using PRINCE2
Directing Successful Projects Using PRINCE2
Next Steps
Q&A
TSO 2008. Content within this presentation may be subject to change.
Progress to date
Nov 06 Public consultation starts
June 07 Public Consultation Report issued
Sep 07 Scoping Document and PDs issued
Oct 07 Design Review
Nov 07 Draft Principles reviewed
Dec 07 Principles updated
Feb 08 Pilots started
Feb 08 to April 08 - Draft Manuscripts reviewed
April 08 Project Board approve recommended changes
TSO 2008. Content within this presentation may be subject to change.
Reasons for change - context
Common Glossary (updated)
Guides
In Development
Portfolio ,
Programme
and Project
Office
( P 3 O )
Updated 2007
M _ o _ R
Gateway
Updated 2007
Refresh underway
PRINCE project 2
MSP programme
Updated 2007
Portfolio Guide
In Development
Models
Portfolio ,
Programme and
Project
Management
Maturity Model
( P 3 M 3 )
PRINCE 2
Maturity Model
( P 2 MM )
Refresh pending
BPUG
PPM
User
group
itSMF
ITIL
User
group
TSO Publishing partner ITIL PPM
Project management for refresh
APMG Accreditation partner ITIL
PPM Exams, training, consultants
TSO 2008. Content within this presentation may be subject to change.
Reasons For Change - mandate
NB, Core Manual size raised to <275 (April 08)
TSO 2008. Content within this presentation may be subject to change.
Study Guides
P2MM / P2MM Guide
Pocket Book
P3M3
PRINCE2
& DSDM
Think PRINCE2
MSP
Business Benefits Through
Project & Programme Management
M_o_R
ITIL
Case Studies
P3O
Knowledge Centre
Proposed Approach
P2MM / P2MM Guide
Business Benefits Through
Project & Programme Management
Managing Successful
Projects Using
PRINCE2
Templates
Checklists
Directing Successful
Projects Using
PRINCE2
Method
TSO 2008. Content within this presentation may be subject to change.
New PRINCE2
TSO 2008. Content within this presentation may be subject to change.
Summary of changes
2005 2009
Principles - 7 Principles
Themes 8 Components 7 Key Themes
Processes 8 Processes 7 Processes
Sub-processes 45 sub-processes -
Techniques 3 techniques
Cross-references to other
BoKs including soft aspects
Management Products 36 products 27 products
The Project Environment - Context rich
Trouble-shooting Hints & Tips Hints & Tips in FAQ style
TSO 2008. Content within this presentation may be subject to change.
What are Principles?
Principles are:
Universal
Self Validating
Empowering
A guiding obligation for good practice
TSO 2008. Content within this presentation may be subject to change.
The PRINCE2 Principles
Business Justification
A PRINCE2 project has continued business justification
Learn Lessons
A PRINCE2 project learns from previous experience
(lessons are sought and recorded throughout)
Roles & Responsibilities
A PRINCE2 project has defined and agreed roles and
responsibilities with an organisation structure that engages
the business, user and supplier stakeholder interests
Managed by Stages
A PRINCE2 project is planned, monitored and controlled on
a stage by stage basis
Managed by Exception
A PRINCE2 project defines tolerances for each project
objective to establish limits of delegated authority
Product Focus
A PRINCE2 project focuses on the definition and delivery of
products, in particular their scope and quality requirements
Tailored
A PRINCE2 project tailors the method to suit its size,
environment, complexity, importance, capability and risk
TSO 2008. Content within this presentation may be subject to change.
PRINCE2 Processes
Processes
Activities
Recommended
Actions
The processes provide the lifecycle based
list of project management activities
TSO 2008. Content within this presentation may be subject to change.
PRINCE2 Processes


Process



Starting Up a Project


Directing a Project


Initiating a Project


Controlling a Stage


Managing Product Delivery


Managing a Stage Boundary


Closing a Project


Pre-
project
Initiation
Stage
Final
Stage
Stage
2, 3, etc
= process applies = process optional
Stage
TSO 2008. Content within this presentation may be subject to change.
Process Model
TSO 2008. Content within this presentation may be subject to change.
What are Key Themes?
Key Themes are:
aspects of project management that need to be
continually addressed. They are not one off
activities
And
aspects of project management that requires
specific treatment for the PRINCE2 processes to be
effective
If the processes are considered as the time-based activity list then the
Key Themes are the reference manual. If the process requires action
the Key Theme provides guidance on how it should be done.
TSO 2008. Content within this presentation may be subject to change.
The PRINCE2 Key Themes
Business Case
Defining the business objectives (the why)
Organisation
Establishing the structure of accountability and
responsibilities (the who)
Quality
Defining and verifying products that are fit-for-purpose (the
what)
Plans
Defining the means of delivering the products (the where and
how, and estimating the when and how much)
Risk
Identifying, assessing and controlling uncertainty (what if)
Change
Managing the integrity of products and making decisions on
issues which may affect the objectives
Progress

Monitoring the achievement of objectives and making
decisions based on actual and forecast progress

TSO 2008. Content within this presentation may be subject to change.
The Project Environment
Embedding Tailoring
Done by the organisation to adopt PRINCE2 Done by the project to adapt the method to the project
context
- size of project
- within a programme
- industry sector (e.g. private/public, customer/supplier)
- type of project (e.g. R&D, policy, construction)
- multi-organisation
- corporate/programme standards (e.g. procurement)
- working with other methods and frameworks
Focus on:
- process ownership
- scaling rules / guidance (e.g. score card)
- Standards (templates, definitions)
- training and development strategy
- integration with business processes and tools
- process assurance
Focus on:
- roles & responsibilities to allocate
- management products to use and how
- number, length and nature of stages
- reporting and reviewing
- tolerances
Guidance in PRINCE2 Maturity Model Guidance in the Method
TSO 2008. Content within this presentation may be subject to change.
Management Products
Philosophy
designed for typical projects
can be scaled up
can be scaled down
Any nesting is explicit
Will be supported by a set of templates
with embedded guidance
and quality criteria
PRINCE2 requires information and decisions, not documents and meetings
TSO 2008. Content within this presentation may be subject to change.
Managing Successful Projects Using PRINCE2 -
Structure
1. Introduction
2. Principles
3. Intro to Processes
4. Starting Up a Project
5. Directing a Project
6. Initiating a Project
7. Controlling a Stage
8. Managing Product Delivery
9. Managing a Stage Boundary
10. Closing a Project
11. Intro to Key Themes
12. Business Case
13. Organisation
14. Quality
15. Plans
16. Risk
17. Change
18. Progress
19. Project Environment
20. Wider Role of the Project Manager
A Product Descriptions
B Product/Process Map
C Roles
D Product Based Planning examples
E Checklists
F - Trouble-shooting




Page count estimate of
275 to 300 published pages
TSO 2008. Content within this presentation may be subject to change.
Directing Successful Projects Using PRINCE2 -
Structure
1. Introduction
2. PRINCE2 Overview
3. Project Board Duties and Behaviours
4. Directing a Project Activities
5. Starting Up a Project
6. Authorising Initiation
7. Authorising a Project
8. Authorising a Stage (or Exception) Plan
9. Giving Ad Hoc Direction
10. Confirming Project Closure
11. Reviewing Benefits

A Role Descriptions
B Product Descriptions
C - Trouble-shooting
D Checklists




Page count estimate of
100 published pages
TSO 2008. Content within this presentation may be subject to change.
Next Steps
Feedback from pilots
Quality Reviews (second draft, final draft)
Surveys to address options and test quality criteria
Proof of Concept (for exam syllabus)
Further consultation (for enhanced exam scheme)
Transition period Q1 2009
TSO 2008. Content within this presentation may be subject to change.
Any Questions?
Warning: this presentation provides a snapshot of the current approach. As
the development is based on continued user consultation the final result
may be different. Always check the website for latest information:

www.best-management-practice.com/PRINCE2Register