prince2: 2009 in practice andy murray, outperform bpug workshops at project challenge are supported...
TRANSCRIPT
PRINCE2: 2009 in PracticeAndy 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
• Agenda– Presentation
• Overview of changes
– Participation!• Brainstorm types of
projects• Define / characterise• Implications• Project Management
approach
©TSO 2008. Content within this presentation may be subject to change.
Summary of changes
2005 2009Principles - 7 Principles
Themes 8 Components 7 Key Themes
Processes 8 Processes 7 Processes
Sub-processes 45 sub-processes -
Techniques 3 techniquesCross-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 PrinciplesBusiness 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
SU
IP
Project Mandate
Authority ToInitiate A Project
Request ToDeliver A Project
Authority ToDeliver A Project
CS
Stage BoundaryApproaching
StageAuthorisation
CP
CompletedWork Package
Authority To DeliverA Work Package
MP
Dir
ecti
on
Man
agem
ent
Del
iver
y
DPException Plan
Request
First StageAuthorisation
Request To Approve Exception Plan
SBSB
Request ToInitiate A Project
Premature Close
ClosureNotification
Request ToClose ProjectRequest To
Close Project
Project EndApproaching
Exception Raised
Request To ApproveNext Stage Plan
Request To ApproveFirst Stage Plan
Co
rpo
rate
Or
Pro
gra
mm
e
Authority ToClose A Project
Stop/GoDecision
New Mandate
ClosureRecommendation
Stage BoundaryApproaching Corrective Action
3.1
©TSO 2008. Content within this presentation may be subject to change.
The PRINCE2 Key Themes
Key Themes
Change
Quality
Progress
Business Case
Organisation
Risk
Plans
Agree the Scope
Agree the Quality
Agree Resources,Costs & Timescales
Agree the Risks Manage the Risks
Control Progress
Control Quality
Control Change
Direct, Manage, Delegate, Communicate
Continued Justification
Baselines: Update the Plans
Key Themes
Change
Quality
Progress
Business Case
Organisation
Risk
Plans
Agree the Scope
Agree the Quality
Agree Resources,Costs & Timescales
Agree the Risks Manage the Risks
Control Progress
Control Quality
Control Change
Direct, Manage, Delegate, Communicate
Continued Justification
Baselines: Update the Plans
©TSO 2008. Content within this presentation may be subject to change.
Applying PRINCE2
Embedding TailoringDone 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?
Construction
IT Infrastructure
Business Change
Procurement (buyer)
R&D
Feasibility
Not-for-profit / social good
Multi-organisations
Software Development
Policy development
Procurement (Seller)
Events
©TSO 2008. Content within this presentation may be subject to change.
SummaryBusiness 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.
www.usergroup.org.uk
0845 0548038
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