Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Version 2.1
PRINCE2®
Maturity Model (P2MM)
www.ogc.gov.uk
PRINCE2® Maturity Model (P2MM)
Contents
Acknowledgements 3
Introduction 4
P2MM Structure 9
PRINCE2 Maturity Model 13
2 Version 2.1
PRINCE2® Maturity Model (P2MM)
Acknowledgements
Reviewer
Alan Harpham – The APM Group Ltd (Project Executive)
The PRINCE2 Maturity Model is derived from the
Portfolio, Programme and Project Management
Maturity Model (P3M3TM) and accordingly the author
would like to acknowledge the significant work done
by those involved in the development of the P3M3.
In particular:
Authoring Team of P3M3
Rod Sowden – Aspire Europe
David Hinley – Enodatum
Steve Clarke – Onemind Management
Editor of P3M3
Sean Redmond
PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries
The OGC logo® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom
Version 2.1 3
PRINCE2® Maturity Model (P2MM)
1. Introduction
Background
The Office of Government Commerce (OGC), owner
of P3M3 and P2MM, is an office of Her Majesty’s
Treasury within the UK government and is responsible
for improving value for money by driving up standards
and capability in public sector procurement. It
achieves this through policy and process guidance,
helping organizations to improve their efficiency and
deliver successfully.
This is the second version of P2MM – the first was
published in April 2004. The new version takes into
account the improvements made to P3M3 and also
reflects the 2009 edition of the PRINCE2 method.
It is fully compatible with the earlier version, so
organizations that have already undertaken P2MM
assessments based on the first version will see the
impact of their existing improvement plans reflected
in future assessments made under the revised model.
It has been identified as version 2.1 to align with the
latest version of P3M3.
Overview of P2MM
The PRINCE2 Maturity Model uses the same structure
as the P3M3 from which it is derived, using:
A five-level maturity framework to characterise the
levels of organizational maturity
Seven process perspectives covering key aspects of
organization-wide project management
Specific and generic attributes for each level of
maturity within each of the process perspectives.
4 Version 2.1
PRINCE2® Maturity Model (P2MM)
Level 1 – Does the organization recognize projects Does the organization recognize projects and
awareness and run them differently from its ongoing run them differently from its ongoing business?
of process business? (Projects may be run informally (Projects may be run informally with no standard
with no standard process or tracking system.) process or tracking system.)
Level 2 – Has the organization adopted PRINCE2 Does the organization ensure that each project
repeatable but allowed the method to be applied is run with its own processes and procedures
process inconsistently across projects within to a minimum specified standard? (There
the organization? may be limited consistency or coordination
between projects.)
Level 3 – Has the organization adopted PRINCE2 and Does the organization have its own centrally
defined embedded it to align to other organizational controlled project processes and can individual
process processes, and can PRINCE2 be tailored to suit projects flex within these processes to suit the
individual projects? particular project?
Level 4 – Does the organization obtain and retain Does the organization obtain and retain specific
managed specific measurements on its PRINCE2 project measurements on its project management
process management performance and run a quality performance and run a quality management
management organization to better predict organization to better predict future
future performance? performance?
Level 5 – Does the organization undertake continuous Does the organization undertake continuous
optimized process improvement with proactive problem process improvement with proactive problem
process and technology management for PRINCE2 and technology management for projects in
projects in order to improve its ability to order to improve its ability to depict performance
depict performance over time and over time and optimize processes?
optimize processes?
Version 2.1 5
PRINCE2® Maturity Model (P2MM)
Level 4 Level 4
6 Version 2.1
PRINCE2® Maturity Model (P2MM)
Level 5
Level 4
Level 3
Level 2
Level 1
Version 2.1 7
PRINCE2® Maturity Model (P2MM)
Uses of P2MM
P2MM can be used in many ways, for example:
to understand the key practices in effective project
management using PRINCE2
to identify the key practices that need to be
embedded within an organization for it to achieve
the next Maturity Level
to understand and improve an organization’s
capability to manage its projects more effectively
using PRINCE2
by client organizations, to assess the risks that
might arise from process capability issues within
service providers managing their projects
by OGC, user groups and the APM Group’s
Accredited Consultancy Organizations as the basis
for developing maturity questionnaires.
Causes of Failure
OGC has carried out extensive research into the
common causes of project failure and how those
causes actually impact on outcomes. The causes of
failure can be grouped into the following categories.
Design and definition failures, where the scope
of the change and the required outcomes and/or
outputs are not clearly defined
Decision-making failures, where there are
inadequate levels of sponsorship and commitment
to the change – i.e. there is no person in authority
able to resolve issues
Discipline failures, such as weak (or no)
arrangements for risk management and an inability
to manage changes in project requirements
Supplier management failures, such as a lack of
understanding of suppliers’ commercial imperatives,
poor management and inappropriate contractual
set-ups
People failures, such as disconnection between
the programme/project and stakeholders, lack of
ownership, and cultural issues.
P2MM Assessments
Organizations can obtain a P2MM assessment of their
maturity either by self-assessment or a formal review.
Self-assessment can be done by simply reviewing
the model and assessing the organization using the
attributes, or by using OGC’s self-assessment tool
to gain a better insight. If using the self-assessment
tool you must use the questions relating to Project
Management, as these are consistent with the
PRINCE2 Maturity Model. The self-assessment tool
can be found at www.p3m3-officialsite.com.
8 Version 2.1
PRINCE2® Maturity Model (P2MM)
2. P2MM Structure
As outlined in Chapter 1, P2MM is based on three Level 1 organizations often over-commit themselves,
core concepts: Maturity Levels, Process Perspectives abandon processes during a crisis, and are unable
and Attributes. This chapter examines each concept to repeat past successes consistently. There is very
in more detail. little planning and executive buy-in, and process
acceptance is limited.
Maturity Levels
The Maturity Levels enable organizations to identify Level 2 – repeatable process
a process improvement pathway along which they The organization will be able to demonstrate,
may choose to travel. This journey should be seen as by reference to particular projects, that basic
a long-term strategic commitment rather than a quick management practices have been established –
fix for immediate tactical problems. Although rapid e.g. tracking expenditure and scheduling resources
short-term improvements can be targeted to achieve – and that processes are developing. There are key
specific goals, the real benefits of P2MM come individuals who can demonstrate a successful track
through continual process improvement. record and that, through them, the organization is
capable of repeating earlier successes in the future.
The five-level hierarchy of P2MM does not imply
that every organization should aim for, or needs to Process discipline is unlikely to be rigorous but, where
achieve, Level 5. Each organization should decide it does exist, projects are performed and managed
which Maturity Level would be optimal for its according to their documented plans, e.g. project
particular business needs at a given time. The highest- status and delivery will be visible to management at
level certificate awarded by the APM Group to date defined points, such as at the end of each stage.
is Level 3.
Top management will be taking the lead on a number
The following sections summarize the characteristics of the projects but there may be inconsistency in the
of each of the five Maturity Levels. Achievements at a levels of engagement and performance.
given level must be maintained and improved upon in
Basic generic training in PRINCE2 and other aspects
order to move up to the next level.
of project management is likely to have been delivered
to key staff.
Level 1 – awareness of process
Processes are not usually documented. There are There is still a significant risk of exceeding cost
no, or only a few, process descriptions. They will and time estimates. Key factors that may have
generally be acknowledged, in that managers may preconditioned the organization to experience
have some recognition of the necessary activities, but difficulties or failure include: inadequate measures
actual practice is determined by events or individual of success; unclear responsibilities for achievement;
preferences, and is highly subjective and variable. ambiguity and inconsistency in business objectives;
Processes are therefore undeveloped, although lack of fully integrated risk management; limited
there may be a general commitment to process experience in change management; and inadequacies
development in the future. in communications strategy.
Undeveloped or incomplete processes mean that
Level 3 – defined process
the necessary activities for better practice are either
The organization’s adoption of PRINCE2 will be
not performed at all or are only partially performed.
documented, standardized and integrated to some
There will be little, if any, guidance or supporting
extent with other business processes. There is likely
documentation, and even terminology may not be
to be PRINCE2 ownership and an established group
standardized across the organization – e.g. business
with responsibility for maintaining consistency and
case, risk, issues, etc. may not be interpreted in the
improvement of the use of PRINCE2 across the
same way by all managers and team members.
organization. Such improvements will be planned
Level 1 organizations may have achieved a number of and controlled, perhaps based on assessments, with
successful projects, but these are often based on key planned development and suitable resources being
individuals’ competencies rather than organization- committed to ensure that they are coordinated across
wide knowledge and capability. In addition, such the organization.
“successes” are often achieved with budget and/or
schedule overruns and, due to the lack of formality,
Version 2.1 9
PRINCE2® Maturity Model (P2MM)
Top management are engaged consistently and It will be a learning organization, propagating the
provide active and informed support. lessons learned from past reviews. The organization’s
ability to rapidly respond to changes and opportunities
There is likely to be an established training programme
will be enhanced by identifying ways to accelerate
to develop the skills and knowledge of individuals
and share learning.
so they can more readily perform their designated
roles. A key aspect of quality management will be the The knowledge gained by the organization from
widespread use of peer reviews of identified products, its process and product metrics will enable it to
to better understand how the PRINCE2 management understand causes of variation and therefore optimize
processes can be improved and thereby eliminate its performance. The organization will be able to show
possible weaknesses. that continuous process improvement is being enabled
by quantitative feedback from its embedded processes
A key distinction between Level 2 and Level 3 is
and from validating innovative ideas and technologies.
the clear adoption of PRINCE2 as the organization’s
There will be a robust framework addressing issues of
project management method. This enables
governance, organizational controls and performance
processes to be managed more proactively using an
management. The organization will be able to
understanding of the interrelationships and measures
demonstrate strong alignment of organizational
of the process and management products. PRINCE2
objectives with business plans, and this will be
can be tailored to suit specific project circumstances,
cascaded down through scoping, sponsorship,
in accordance with guidelines.
commitment, planning, resource allocation, risk
management and benefits realization.
Level 4 – managed process
Level 4 is characterized by mature behaviour and
Process Perspectives
PRINCE2 processes that are quantitatively managed
There are seven Process Perspectives within P2MM,
– i.e. controlled using metrics and quantitative
defining the key characteristics of a mature
techniques. There will be evidence of quantitative
organization. Each perspective describes the processes
objectives for quality and process performance,
and practices that should be deployed at a given level
and these will be used as criteria in managing the
of maturity. As organizations move up through the
PRINCE2 processes. The measurement data collected
Maturity Levels, the quality and effectiveness of the
will contribute towards the organization’s overall
processes and practices increase correspondingly.
performance measurement framework and will
This incremental nature of process improvement is a
be imperative in analyzing the organization’s
key feature of P2MM.
projects and ascertaining the current capacity
and capability constraints. The following sections outline the seven Process
Perspectives and give a summary of their
Top management will be committed, engaged
characteristics.
and proactively seeking out innovative ways to
achieve goals.
Management Control
Using process metrics, management can effectively This covers the internal controls of the project and
control the PRINCE2 processes and identify ways to how its direction of travel is maintained throughout
adjust and adapt them to particular initiatives without its life cycle, with appropriate stages to enable it
loss of quality. Organizations will also benefit through to be stopped or redirected by a controlling body
improved predictability of process performance. if necessary.
Management control is characterized by clear
Level 5 – optimized process
evidence of leadership and direction, scope, stages
The organization will focus on optimization of its
and review processes during the course of the project.
quantitatively managed PRINCE2 processes to take
There will be regular Highlight Reports and clearly
into account changing business needs and external
defined decision-making processes. There will be
factors. It will anticipate future capacity demands and
full and clear objectives and descriptions of what
capability requirements to meet delivery challenges.
the project will deliver. Projects should have clearly
Top managers are seen as exemplars, reinforcing described outputs.
the need and potential for capability and
Internal structures will be aligned to achieve these
performance improvement.
characteristics and the focus of control will be on
achieving them within the tolerances set by corporate
or programme management and based on the
10 Version 2.1
PRINCE2® Maturity Model (P2MM)
Version 2.1 11
PRINCE2® Maturity Model (P2MM)
Resource Management
Resource management covers management of all
types of resources required for delivery. These include
human resources, buildings, equipment, supplies,
information, tools and supporting teams. A key
element of resource management is the process for
acquiring resources and how supply chains are utilized
to maximize effective use of resources. There will be
evidence of capacity planning and prioritization to
enable effective resource management. This will also
include performance management and exploitation
of opportunities for greater utilization. Resource
capacity considerations will be extended to the
capacity of the operational groups to resource the
implications of change.
Attributes
Within each Process Perspective are a number of
attributes. These are indicators of process and
behavioural maturity. Specific Attributes relate only
to a particular Process Perspective, while Generic
Attributes apply equally to all Process Perspectives
at each of the five Maturity Levels.
Inevitably, organizations will perform well against
some Process Perspectives and not so well against
others. Attributes describe the intended profile of
each Process Perspective at each Maturity Level,
and the topics, processes and practices covered will
change and build as the Maturity Level changes.
Conclusion
The structure of P2MM allows organizations to see a
snapshot of where they are now with respect to any
of the Process Perspectives in their PRINCE2 project
management capabilities. This, along with knowledge
of where the organization needs or wants to be in
the future, provides the basis for an improvement plan
to be devised and for progress towards the target to
be tracked.
The remaining chapter looks at the PRINCE2 Maturity
Model in more detail.
12 Version 2.1
PRINCE2® Maturity Model (P2MM)
This model is based on the 2009 edition of OGC’s Furthermore, a PRINCE2 project displays evidence of
PRINCE2 publications, along with experience gained the principles on which PRINCE2 is based. These seven
from the Project Management Maturity Model and principles can be summarized as follows:
the original version of P3M3.
Continued business justification. A PRINCE2 project
has continued business justification
Definition of PRINCE2 Project Management
PRINCE2 defines a project as a temporary organization Learn from experience. PRINCE2 project teams
that is created for the purpose of delivering one learn from previous experience: lessons are sought,
or more business products according to an agreed recorded and acted upon throughout the life of
Business Case. the project
Project management is the planning, delegating, Defined roles and responsibilities. A PRINCE2
monitoring and control of all aspects of the project, project has defined and agreed roles and
and the motivation of those involved, to achieve the responsibilities within an organization structure
project objectives within the expected performance that engages the business, user and supplier
targets for time, cost, quality, scope benefits and risk. stakeholder interests
Manage by stages. A PRINCE2 project is planned,
Characteristics of PRINCE2 project management
monitored and controlled on a stage-by-stage basis
There are a number of characteristics of project work
that distinguish it from business as usual. These can Manage by exception. A PRINCE2 project has
be summarized as: defined tolerances for each project objective to
establish limits of delegated authority
Change. Projects are the means by which we
introduce change Focus on products. A PRINCE2 project focuses on
the definition and delivery of products, in particular
Temporary. As the definition above states, projects
their quality requirements
are temporary in nature. Once the desired change
has been implemented, business as usual resumes Tailor to suit the project environment. PRINCE2
(in its new form) and the need for the project is is tailored to suit the project’s environment, size,
removed. Projects should have a defined start and a complexity, importance, capability and risk.
defined end
Attributes of PRINCE2 Project Management
Cross-functional. Projects involve a team of
The following sections set out the attributes for each
people with different skills working together (on
of the seven Process Perspectives within the PRINCE2
a temporary basis) to introduce a change that will
Maturity Model at each of the five Maturity Levels,
impact upon others outside of the team. Projects
along with a description of each attribute.
often cross the normal functional divisions within
an organization and sometimes span entirely
different organizations. This frequently causes
stresses and strains both within and between
organizations, for example, between customers
and suppliers. Each has a different perspective and
motivation for getting involved in the change
Unique. Every project is unique. An organization
may undertake many similar projects, and establish
a familiar, proven pattern of project activity, but
each one will be unique in some way: a different
team, a different customer, a different location. All
these factors combine to make every project unique
Uncertainty. Clearly, the characteristics already listed
will introduce threats and opportunities over and
above those typically encountered in the course of
business as usual. Projects are more risky.
Version 2.1 13
PRINCE2® Maturity Model (P2MM)
14 Version 2.1
PRINCE2® Maturity Model (P2MM)
4. Local reviews, with some corrective actions 8. Project products accord with Product
undertaken within the group Descriptions and are reviewed against agreed
quality criteria that match the project’s
5. Generic training may be provided in key
Acceptance Criteria and are traceable
concepts, and there may be individuals
throughout project life cycle
undertaking qualification training
9. Product or service handover to the operational
6. Local sharing of knowledge may exist but
and maintenance environment planned during
mostly ad hoc
the Initiation Stage
7. Key individuals may have practical delivery
10. Project Boards with business, user and supplier
experience and track record
representation exist and have clearly defined
8. Roles, responsibilities and competencies roles and responsibilities, based on PRINCE2
defined in some areas but not consistently
11. End stage assessments planned and undertaken
across the organization
at appropriate stages in project life cycle,
9. Plans exist but are not underpinned by consistent perhaps involving members of other teams,
development methodology, yet may still be the business and external reviewers
effective locally
12. There will be active consideration of transition
10. Planning seen as activity tracking rather than management to ensure that project products are
proactive/forecasting capable of being exploited by the Senior User
11. Estimation is more “guesstimation” and does
Generic Attributes
not use standard techniques
1. Information has a refresh cycle or is regularly
accessed
P2MM - Management Control – Level 3
2. Organization-wide information standards on
Description
confidentiality, availability and integrity
PRINCE2 provides the centrally defined and
documented approach to a project management life 3. Formal information release management
cycle and controls, and it is applied in all projects by procedures
capable staff who support project teams.
4. Independent reviews take place
Specific Attributes 5. Scrutiny largely for compliance reasons,
1. PRINCE2 adopted across the organization, identifying failures rather than opportunities
with supporting documentation and end stage for improvement
assessments to maintain control followed by
6. Plans developed to a central and consistent
all projects
standard that is output- or goal-based
2. Issue management and change control
7. Plan development takes into account a range
procedure integrated and consistent across
of relevant factors
the organization
8. Evidence of effective estimating techniques
3. Project Managers accustomed to tailoring
PRINCE2 to meet needs of specific projects 9. Dependencies are identified, tracked and
managed effectively
4. Projects ensure that it is feasible to deliver
solutions that satisfy relevant requirements 10. Training is focused on the organization’s
approaches and raising competence of
5. Variations to project products subject to issue
individuals in specific roles
and change control procedure and approved
as appropriate 11. Forums exist for sharing organizational
experience to improve individual and
6. Standard processes, procedures and templates,
organizational performance
based on PRINCE2, to enable consistent
management control of projects 12. Centrally managed role definitions and
sets of competencies defined and used to
7. Decisions to hand over of products to the
support appointments
operation and maintenance environment signed
off by the Executive and Senior User roles
Version 2.1 15
PRINCE2® Maturity Model (P2MM)
16 Version 2.1
PRINCE2® Maturity Model (P2MM)
Version 2.1 17
PRINCE2® Maturity Model (P2MM)
18 Version 2.1
PRINCE2® Maturity Model (P2MM)
6. Clear and active ownership of plans to improve 4. Decisions taken to balance benefits and
performance from project outputs “dis-benefits” based on statistical measures
7. Procedures for management of benefits 5. Strategic priorities affect benefit measures (e.g.
realization owned, reviewed and being improved changes to strategic Key Performance Indicators
are filtered down into projects)
8. The organization ensures that claimed benefits
are realistic and endorsed by the project 6. Post-project benefit reviews studied, trends
Executive and Senior User established, and lessons learned fed back
into benefits realization planning and other
Generic Attributes management activities
1. Information is current and extensively referenced
for better decision-making Generic Attributes
1. Information is valued, with continual
2. Trend analysis and measurement undertaken
maintenance and reference
on performance information to identify
improvement opportunities 2. Evidence of extensive intelligence-gathering
processes, with information disseminated
3. Knowledge management is a central function
through a variety of channels
and is used to help improve performance
and planning 3. Review and improvement is continual and
proactive, with lessons being shared openly
4. Reviews focus on opportunities to improve as
well as compliance 4. Planning inherent in decision-making process,
with adjustments and implications managed
5. Plans kept up to date, with the application
and deployed
of sophisticated planning techniques and
recognition of interdependencies 5. Active management of interdependencies
between initiative plans and other business plans
6. Extensive training is provided, focusing on
personal development and performance 6. Estimations are accurate and used effectively to
improvement ensure delivery
7. Evidence of interventions to avoid conflicts 7. High levels of competence embedded in all roles
and take advantage of opportunities and seen as part of career paths
8. Mentoring and individual development is used 8. Knowledge transfer is an inherent behaviour
to improve organizational performance within the organization
9. Succession plans exist for key roles 9. Skills embedded into organizational leadership
and management development programmes
P2MM - Benefits Management – Level 5
Description P2MM - Financial Management – Level 1
Benefits management is embedded within the Description
organizational approach to change and is assessed as There is little or no financial control at project level.
part of the development of organizational strategy. There is a lack of accountability and monitoring of
project expenditure.
Business performance metrics are linked to, and
underpin, the recognition of benefits realization.
Specific Attributes
There is evidence of continual improvement.
1. Projects poorly defined and difficulties
experienced in setting realistic budgets
Specific Attributes
1. Clear links between strategic decision-making 2. No procedure for projects to bid for funds
and benefits realization
3. Projects lack control mechanisms to track costs
2. Evidence of development and innovation and project expenditure
of techniques based on experience of
4. Little formal project investment appraisal,
realizing a variety of benefits in several
with formal Business Cases rarely submitted
different environments
and monitored
3. Active management of opportunities to enhance
5. Operational input costs assumed and not
benefits realization
accounted for
Version 2.1 19
PRINCE2® Maturity Model (P2MM)
20 Version 2.1
PRINCE2® Maturity Model (P2MM)
Version 2.1 21
PRINCE2® Maturity Model (P2MM)
22 Version 2.1
PRINCE2® Maturity Model (P2MM)
Version 2.1 23
PRINCE2® Maturity Model (P2MM)
24 Version 2.1
PRINCE2® Maturity Model (P2MM)
4. Planning inherent in decision-making process, 6. Plans, if any, are conceptual or merely sequences
with adjustments and implications managed of events with rough timescales
and deployed
7. Planning, if any, likely to be an initial activity with
5. Active management of interdependencies little maintenance of ownership or tracking
between initiative plans and other business plans
6. Estimations are accurate and used effectively P2MM - Risk Management – Level 2
to ensure delivery Description
Risk management is recognized and used on projects,
7. High levels of competence embedded in all roles
but there are inconsistent approaches, which result in
and seen as part of career paths
different levels of commitment and effectiveness.
8. Knowledge transfer is an inherent behaviour
within the organization Specific Attributes
1. Different areas and projects manage risk in
9. Skills embedded into organizational leadership
different ways
and management development programmes
2. Some projects recognize different categories
of risk (e.g. distinguishing between project and
P2MM - Risk Management – Level 1
operational risks)
Description
There is minimal evidence of risk management being 3. Risk response strategies and plans are likely to
used to any beneficial effect on projects. have been ineffective in the past
There may be evidence of risks being documented but 4. Inconsistency of approach to the assessment
little evidence of active management. of risks
5. Risk Register based on an organizational
Specific Attributes
template may be used, but escalation and
1. Some risks may be identified and associated
communication on risks outside the project
with particular projects, but are not described
may be ineffective
or registered consistently, and there will be
little, if anything, in terms of an effective risk 6. Local risk management procedures in place and
management procedure managed by Project Board and the rest of the
project management team
2. Focus of management attention is on dealing
with issues as they arise, with a reactive rather 7. Risk management not aligned with other project
than proactive approach life cycle activities (e.g. initiation and end stage
assessments)
3. Risks arbitrarily classified and rarely, if ever,
quantified 8. Risk status reported in Highlight Reports to
Project Board on ad hoc basis, if at all
4. Risk identification likely to be a one-off activity
during project initiation, and risks unlikely to be 9. Key Project Managers understand and
tracked or re-assessed during project life cycle articulate the purpose and importance of
risk management, but inconsistent levels of
5. Foreseeable threats likely to impact on projects
commitment and understanding across all
6. Little, if any, communication with other parts of projects or the organization
the organization concerning project risk
Generic Attributes
Generic Attributes 1. Localized information structures, with some
1. Training provision is uncoordinated, with little or information sharing between teams
no knowledge sharing
2. Focus on documentation during start-up and
2. Key individuals lack experience definition, but not maintained over initiative’s
life cycle
3. No standard roles, and responsibilities are not
defined or are generic 3. Limited localized information controls, with no
formal release management arrangements
4. Some information available but is outdated,
unstructured and dispersed 4. Local reviews, with some corrective actions
undertaken within the group
5. Limited, if any, formal checking or review
Version 2.1 25
PRINCE2® Maturity Model (P2MM)
5. Generic training may be provided in key 10. Risk assessment techniques defined and
concepts, and there may be individuals deployed consistently
undertaking qualification training
Generic Attributes
6. Local sharing of knowledge may exist but
1. Information has a refresh cycle or is regularly
mostly ad hoc
accessed
7. Key individuals may have practical delivery
2. Organization-wide information standards on
experience and track record
confidentiality, availability and integrity
8. Roles, responsibilities and competencies defined
3. Formal information release management
in some areas but not consistently across the
procedures
organization
4. Independent reviews take place
9. Plans exist but are not underpinned by consistent
development methodology, yet may still be 5. Scrutiny largely for compliance reasons,
effective locally identifying failures rather than opportunities
for improvement
10. Planning seen as activity tracking rather than
proactive/forecasting 6. Plans developed to a central and consistent
standard that is output- or goal-based
11. Estimation is more “guesstimation” and does
not use standard techniques 7. Plan development takes into account a range
of relevant factors
P2MM - Risk Management – Level 3 8. Evidence of effective estimating techniques
Description
9. Dependencies are identified, tracked and
Project risk management is based on a centrally
managed effectively
defined process that is cognizant of the organization’s
policy for the management of risks and is used 10. Training is focused on the organization’s
consistently. approaches and raising competence of
individuals in specific roles
Specific Attributes
11. Forums exist for sharing organizational
1. Standard Risk Management Strategy, Risk
experience to improve individual and
Register and risk management tools and
organizational performance
techniques used extensively and consistently
12. Centrally managed role definitions and
2. Risks identified (in terms of their cause, event
sets of competencies defined and used to
and effect), assessed (for probability, impact
support appointments
and proximity) and controlled in accordance
with the PRINCE2 risk management procedure,
across all projects P2MM - Risk Management – Level 4
Description
3. Regular reviews, addressing broader
Project risk management is working effectively,
opportunities for improvement as well
is embedded, and the value of risk management
as compliance
can be demonstrated.
4. Reviews seen as a positive opportunity to
There is evidence of opportunity management and
improve, not a threat
management of risk aggregation.
5. Risk management interventions embedded
within project life cycle Specific Attributes
1. Projects able to demonstrate resource and
6. Risks consistently categorized by type
budgetary implications of risks throughout
(e.g. commercial, operational or strategic)
project life cycle
7. Audits of risk within projects
2. Cost effectiveness and feasibility of responses
8. Exception Reports used for escalation of demonstrable across all projects
project risks
3. Audits of risk management effectiveness
9. Risks not limited to internal impact on
4. Aggregated risk levels across projects tracked
project goals
and managed
26 Version 2.1
PRINCE2® Maturity Model (P2MM)
5. Clear understanding of level of risk exposure 3. Risk assessment underpins all decision-making
from projects being undertaken
4. Projects ensure adequate consideration of
6. Evidence of lessons being learned from project business continuity, especially on handover to
reviews and assurance reviews the operational and/or maintenance environment
7. Risk management seen as organizational, 5. Evidence of opportunity risks being actively
with clear ownership managed
8. May be a risk manager, providing guidance 6. Organizational risk management policy
and controls and process guide periodically reviewed
for effectiveness
9. Evidence of decision-making based on risk
assessment 7. Business intelligence informs risk management
and has clear cascade and escalation route
10. The business and project stakeholders generally
feel comfortable with the management of 8. Strong links and integration with financial
project risks, and are involved as appropriate management, planning, estimating, project
control and governance procedures, and risks to
Generic Attributes project benefits are highlighted and examined
1. Information is current and extensively referenced
for better decision-making Generic Attributes
1. Information is valued, with continual
2. Trend analysis and measurement undertaken
maintenance and reference
on performance information to identify
improvement opportunities 2. Evidence of extensive intelligence-gathering
processes, with information disseminated
3. Knowledge management is a central function
through a variety of channels
and is used to help improve performance
and planning 3. Review and improvement is continual and
proactive, with lessons being shared openly
4. Reviews focus on opportunities to improve
as well as compliance 4. Planning inherent in decision-making process,
with adjustments and implications managed
5. Plans kept up to date, with the application
and deployed
of sophisticated planning techniques and
recognition of interdependencies 5. Active management of interdependencies
between initiative plans and other business plans
6. Extensive training is provided, focusing on
personal development and performance 6. Estimations are accurate and used effectively to
improvement. ensure delivery
7. Evidence of interventions to avoid conflicts 7. High levels of competence embedded in all roles
and take advantage of opportunities and seen as part of career paths
8. Mentoring and individual development is used 8. Knowledge transfer is an inherent behaviour
to improve organizational performance within the organization
9. Succession plans exist for key roles 9. Skills embedded into organizational leadership
and management development programmes
P2MM - Risk Management – Level 5
Description
Risk management is embedded in the organizational
culture and underpins all decision-making within
projects. There is evidence of continual improvement.
Specific Attributes
1. Accountability for management of risk at
Executive Board level
2. Executive Board has clear visibility of risk
exposure to the organization from projects
Version 2.1 27
PRINCE2® Maturity Model (P2MM)
28 Version 2.1
PRINCE2® Maturity Model (P2MM)
Version 2.1 29
PRINCE2® Maturity Model (P2MM)
8. Evidence of ideas and requirements being 5. Pre-emptive and rational project closure based
scheduled and built into organizational on business decisions other than project
strategic planning performance
9. Decisions to start-up and initiate projects made 6. Lessons learned contribute to development of
against impact assessment on current initiatives guidance on conduct of specific roles
7. Projects aligned to organization’s strategic plans
Generic Attributes
1. Information is current and extensively referenced 8. Formal ideas management process exists, with
for better decision-making ideas deferred or built into strategy where
appropriate
2. Trend analysis and measurement undertaken
on performance information to identify 9. Executive Board-level reaction to, and
improvement opportunities management of, business performance relating
to project-initiated activities
3. Knowledge management is a central function
and is used to help improve performance 10. High levels of competence in project and change
and planning management evident at Executive Board level
4. Reviews focus on opportunities to improve as 11. Leadership development programme includes
well as compliance PRINCE2 and project management education
5. Plans kept up to date, with the application 12. Structured management of knowledge, with
of sophisticated planning techniques and lessons being identified, learned and embedded
recognition of interdependencies
13. Business performance actively tracked and
6. Extensive training is provided, focusing on managed, with timely interventions
personal development and performance
14. PRINCE2 and project management embedded as
improvement
core change management techniques
7. Evidence of interventions to avoid conflicts and
15. Regular periodic reviews of effectiveness of
take advantage of opportunities
governance arrangements, based on lessons
8. Mentoring and individual development is used to
improve organizational performance Generic Attributes
1. Information is valued, with continual
9. Succession plans exist for key roles
maintenance and reference
2. Evidence of extensive intelligence-gathering
P2MM - Organizational Governance – Level 5
processes, with information disseminated
Description
through a variety of channels
The governance arrangements for projects are a core
aspect of organizational control, with demonstrable 3. Review and improvement is continual and
reporting lines to Executive Board level and with clear proactive, with lessons being shared openly
ownership and control responsibilities embedded
4. Planning inherent in decision-making process,
within the organization.
with adjustments and implications managed
There is evidence of continual improvement. and deployed
5. Active management of interdependencies
Specific Attributes
between initiative plans and other business plans
1. Projects signed off at Executive Board level, as
appropriate 6. Estimations are accurate and used effectively to
ensure delivery
2. Organizational governance and accountabilities
reflected throughout the organization, down to 7. High levels of competence embedded in all roles
specific project roles and responsibilities and seen as part of career paths
3. Legal and regulatory responsibilities have 8. Knowledge transfer is an inherent behaviour
visible compliance within the organization
4. Decisions on priorities and major conflict 9. Skills embedded into organizational leadership
resolution resolved by reference to strategic and management development programmes
priorities and Executive Board
30 Version 2.1
PRINCE2® Maturity Model (P2MM)
Version 2.1 31
PRINCE2® Maturity Model (P2MM)
32 Version 2.1
PRINCE2® Maturity Model (P2MM)
Specific Attributes
1. Active strategies for development of internal
capacity and capability
2. The organization will have an explicit policy for
improving its technical capability and will have
improvement plans that recognize business
demands and constraints
3. Flexible resource availability and movement
between projects, programmes and operations
4. Resource allocation based on resource availability
and competency requirements across projects
5. Project Managers have an understanding of
business processes and objectives and are able
to ensure that project resources are sufficiently
focused on business needs
6. Senior management ownership of capability
building and associated risks
7. Active supply chain collaboration to deploy and
utilize optimal set of skills in projects
Generic Attributes
1. Information is valued, with continual
maintenance and reference
2. Evidence of extensive intelligence-gathering
processes, with information disseminated
through a variety of channels
3. Review and improvement is continual and
proactive, with lessons being shared openly
4. Planning inherent in decision-making process,
with adjustments and implications managed
and deployed
5. Active management of interdependencies
between initiative plans and other business plans
6. Estimations are accurate and used effectively to
ensure delivery
7. High levels of competence embedded in all roles
and seen as part of career paths
8. Knowledge transfer is an inherent behaviour
within the organization
9. Skills embedded into organizational leadership
and management development programmes
Version 2.1 33
OGC 1 Horse Guards Road, The Service Desk will also
London SW1A 2HQ channel queries to the
appropriate second-line
About OGC support. We look forward
The Office of Government to hearing from you.
Commerce is an independent
You can contact the Service
office of HM Treasury.
Desk 8am – 6pm Monday
The OGC logo is a registered to Friday:
trademark of the Office of
T: 0845 000 4999
Government Commerce
E: ServiceDesk@ogc.gsi.gov.uk
in the United Kingdom and
www.ogc.gov.uk
other countries.
Press enquiries
OGC Service Desk
T: 020 7271 1318
OGC customers can contact
F: 020 7271 1345
the central OGC Service Desk
about all aspects of
OGC business.
CP0259/01/10