Transcript Name of Workshop Name, Company

PRINCE2: 2009 in Practice
Andy Murray, Outperform
BPUG Workshops at Project Challenge are supported by:
Workshop
• Objectives
– Explain how the
universal approach in
PRINCE2 2009
– Explore how PRINCE2
can be applied to
different project types
• Size
• Complexity
• Purpose
©TSO 2008. Content within this presentation may be subject to change.
• Agenda
– Presentation
• Overview of changes
– Participation!
• Brainstorm types of
projects
• Define / characterise
• Implications
• Project Management
approach
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
Management
Products
36 products
25 products
The Project
Environment
-
Context rich
©TSO 2008. Content within this presentation may be subject to change.
New PRINCE2
©TSO 2008. Content within this presentation may be subject to change.
The PRINCE2 Principles
Business Justification
A PRINCE2 project must have continued business
justification
Roles & Responsibilities
A PRINCE2 project must have defined and agreed roles
and responsibilities with an organisation structure that
engages the business, user and supplier stakeholder
interests
Product Focus
A PRINCE2 project must focus on products and their
quality
Managed by stages
A PRINCE2 project must be planned, baselined,
monitored and controlled on a stage by stage basis
Management of risk
A PRINCE2 project must proactively manage its risk
Scaling and tailoring
A PRINCE2 project must decide how to apply the
method such that it is scaled and tailored to suit the
project’s environment, complexity, importance and risk
Learning lessons
A PRINCE2 project must learn from experience
©TSO 2008. Content within this presentation may be subject to change.
Process Model
New
Mandate
Closure
Notification
Stop/Go
Decision
Project Mandate
Direction
Corporate Or
Programme
3.1
Authority To
Deliver A Project
Authority To
Initiate A Project
Exception Plan
Request
First Stage
Authorisation
Stage
Authorisation
Premature
Close
Authority To
Close A Project
Request To Approve
Exception Plan
Request To
Initiate A Project
Management
SU
Request To
Deliver A Project
Request To Approve
First Stage Plan
Request To Approve
Next Stage Plan
SB
SB
Stage Boundary
Approaching
Corrective Action
IP
Closure
Recommendation
CP
Exception
Raised
Stage Boundary
Approaching
CS
Delivery
Authority To Deliver
A Work Package
Completed
Work Package
MP
©TSO 2008. Content within this presentation may be subject to change.
Project End
Approaching
DP
The PRINCE2 Key Themes
Key Themes
Business Case
Continued Justification
Organisation
Plans
Risk
Change
Quality
Progress
Direct, Manage, Delegate, Communicate
Update the Plans
Baselines:
Agree the Risks
Agree the Scope
Agree the Quality
Agree Resources,
Costs & Timescales
©TSO 2008. Content within this presentation may be subject to change.
Manage the Risks
Control Change
Control Quality
Control Progress
Applying PRINCE2
Embedding
Tailoring
Done by the organisation
- Adapting to organisational context
Done by the project
- Adapting to the project context
Focus on:
- process ownership
- scaling rules / guidance (e.g. score card)
- Standards (templates, definitions)
- training and development strategy
- integration with business processes
- tools
- process assurance
Focus on:
- roles & responsibilities to allocate
- management products to use
- number of stages (and nature)
- variations from organisational standards
- specialist methods to use
- reporting and reviewing
- team capabilities
Guidance in P2MM
Guidance in the Method and P2iP
©TSO 2008. Content within this presentation may be subject to change.
Types of Projects?
Not-for-profit / social good
Business Change
Construction
IT Infrastructure
Multi-organisations
Procurement (Seller)
R&D
Policy development
Procurement (buyer)
Feasibility
Events
Software Development
©TSO 2008. Content within this presentation may be subject to change.
Summary
Business Justification
A PRINCE2 project must have continued business
justification
Roles & Responsibilities
A PRINCE2 project must have defined and agreed roles
and responsibilities with an organisation structure that
engages the business, user and supplier stakeholder
interests
Product Focus
A PRINCE2 project must focus on products and their
quality
Managed by stages
A PRINCE2 project must be planned, baselined,
monitored and controlled on a stage by stage basis
Management of risk
A PRINCE2 project must proactively manage its risk
Scaling and tailoring
A PRINCE2 project must decide how to apply the
method such that it is scaled and tailored to suit the
project’s environment, complexity, importance and risk
Learning lessons
A PRINCE2 project must learn from experience
©TSO 2008. Content within this presentation may be subject to change.
Best Practice User Group™ aims to be the official user
group of choice for programmes, projects and risks.
Our mission: To help users adopt, use, share and
shape the application of OGC PPM Products
www.usergroup.org.uk
0845 0548038
[email protected]