p3o foundation workbook - the knowledge academy · simply implementing a p3o ® model will not...
TRANSCRIPT
0
P30 Foundation
Workbook
The Knowledge academy
Instructions to Follow
Please follow the below Instructions before reading this workbook:
1. Open workbook in Adobe Reader or any other pdf reader
2. Write your answer and Save the pdf by pressing Ctrl+S
3. Upload this workbook at the time you request for the exam
1
Contents Introduction .............................................................................................................................. 3
Introduction to P3O ® ............................................................................................................ 3
Introduction to a Project ....................................................................................................... 4
Introduction to Project Management ................................................................................... 4
Introduction to a Programme ................................................................................................ 5
Introduction to Programme Management ............................................................................ 5
Introduction to a Portfolio .................................................................................................... 6
Introduction to a Portfolio Management .............................................................................. 6
Individual, Collaborative, and Integrated Working Methods ................................................ 8
Benefits of Standard Tools & Techniques .............................................................................. 8
Benefits of Project Management .......................................................................................... 9
Multiple Choice Questions 1: .............................................................................................. 10
Strategic Objectives ................................................................................................................. 12
What are P3O ®s? .................................................................................................................... 14
Portfolio, Programme and Project Lifecycles ...................................................................... 17
Portfolio Delivery Cycle ....................................................................................................... 18
Quality Assurance ................................................................................................................ 21
Multiple Choice Questions 2: .............................................................................................. 23
Key Performance Indicators .................................................................................................... 25
Maturity Levels .................................................................................................................... 25
Multiple Choice Questions 3 ............................................................................................... 30
2
Introduction
Introduction to P3O ®
A P3O ® (Portfolio, Programme and Project Offices) model offers a decision‐
enabling or delivery support structure for all change within an organisation.
The aim of P3O ® is to provide universally appropriate guidance that will
enable individuals as well as organisations to establish, develop and maintain
suitable business support structures.
The following are some benefits of P3O ®:
i. Identification and realisation of business results and benefits through
programmes.
ii. Successful delivery of project outputs that aid benefits within time,
quality and cost restraints.
iii. Informed senior management decision‐making on factors such as
strategy, prioritisation, risk management and optimisation of resources
in order to successfully deliver their business objectives i.e. portfolio
management.
3
Introduction to a Project
A project is a short and one‐time exercise whose duration varies. It is
dedicated to meeting an organisation's particular needs to develop a service
or to change a business method. It is in direct contrast to how a company
usually operates continuously to produce its products or services. For
example, an organisation's task may be to produce vehicles continuingly, and
the task or work is called functional because the company produces over‐
and‐over again the same goods or services and employees maintain their
jobs semi‐permanently.
Introduction to Project Management
A perceived need generally initiates a project in an organisation. As a one‐off
project, it will have a beginning and an end, expenditure limitations, time and
tools and includes a purpose‐built team. Project teams consist of several
team leaders from end users/customers, Information technology staff, a
leader of a project, trainers, project manager, sponsor and other
stakeholders.
Project management is the practice of handling all the numerous project
resources and facets in a way that the resources provide all the performance
needed to accomplish the project within the specified scope, time, and cost
constraints.
This should be accepted at the beginning point of the project, and by the
time the project starts both stakeholders and team leaders should have a
strong understanding and approval of the procedure, approach and planned
results. A successful project manager uses a structured framework that can
be audited and utilised for the project as a blueprint, and this is done by
applying a technique by project management.
4
Introduction to a Programme
A programme's primary aim is to understand the results and advantages of
decisive importance. A programme is a temporary, adaptable company
developed to organise, manage and supervise the implementation of a
collection of similar projects and tasks to fulfil results and profits related to
the strategic objectives of an organisation.
A programme is likely to have a life that spans several years. A programme
offers advantages by a change to an organisation, and it is based on an
accepted idea of how a company or an organisation will go ahead in the
future. Programme Management offers a well‐organised process for
organising, planning, aligning, handling and monitoring the tasks involved.
Introduction to Programme Management
Programme management is the co‐ordinated management of projects and
change management activities to achieve beneficial change. A programme
usually starts with a vision of a changed organisation and the benefits that
accrue from the change. Delivering the changed organisation will involve
coordinating a number of projects and ensuring that their outputs are used
to deliver benefits.
Programmes connect the delivery of change to the strategic goals and
direction of the organisation. Programme management is intended to
manage the organisation within its changing environment, refining and re‐
focussing as needed along the way. Programmes are concerned with
delivering results, whereas projects are focussed on outputs.
Some of the important documents connected with a well‐managed
programme are:
5
Programme Mandate Programme Brief Programme Definition
Introduction to a Portfolio
The word Portfolio is utilised to define an organisation's overall collection of
programmes and projects. Portfolio Management is a coordinated set of
strategic processes and decisions that commonly allow the most efficient
balance of organisational change and business as usual/operations.
Introduction to a Portfolio Management
Portfolio management includes gathering appropriate details on the
investment plans of the company in one place, including programmes and
projects, and aligning their execution with strategic goals, business
specifications and the capability of the organisation.
It should not just consider those programme and project commitments
comprising the organisation’s change program, in terms of resources, but
should also find the broader business picture‐taking account of Business as
Usual (/operations). Only by understanding and appreciating the
organisation’s full suite of commitments can a fully balanced business
portfolio be achieved.
In this context Business, as Usual, is defined as the things done to keep the
business operating day‐to‐day. By understanding the demands on Business
as Usual, its lifecycles and critical events, the delivery of change through
programmes and projects can be timed and managed to ensure the least
disruption.
6
Difference between a Project, a Programme and a Portfolio
Project Programme Portfolio
Scope Projects have
defined
objectives.
Scope is
progressively
elaborated
throughout
the project
life cycle
Programme
have larger
scope and
provide more
significant
benefits
Portfolio
have a
business
scope that
changes with
the strategic
goals of the
organisation
Duration Temporary
(short time
duration)
Temporary (can
last for many
years)
Permanent
(continually
changing )
Management Project Level
plans with
focus on
detailed
delivery using
stage plans
High level plans
supported by
detailed plans
Ongoing
process of
prioritising
and aligning
the Portfolio
to meet
strategic
objective
Success Success is
measured by
product and
project
quality
Success is
measured by
the degree to
which the
program
satisfies the
needs and
benefits for
which it was
undertaken
Success is
measured in
terms of
aggregate
performance
of portfolio
components
7
Individual, Collaborative, and Integrated Working Methods
Individual: Where only one person uses the tools (usually the project manager). There may be multiple installations, but the relationship is one business change initiative to one user. Desktop applications such as project planning software is an example, spreadsheets and word processor are others. Collaborative: Where multiple users access a single set of information through a tool. There may be multiple installations of the tool, but the relationship is one business change initiative to multiple users. Web‐based portals and applications that share information and processes through a centralised server are examples. Integrated: Where multiple people access multiple sets of information in some manner through a tool. There is generally a single installation or application of the tool across the organisation, with partitions for business change initiatives and the ability to link information in a hierarchical manner. The relationship is multiple business change initiatives to multiple users. Enterprise PPM solutions provides integrated reports for multiple users from a single set of data
Benefits of Standard Tools & Techniques
Automation of business processes
Improved compliance with business processes
Improved timeliness of decision‐support information
Improved quality of decision‐support information
Improved decision‐making
Improved management across geography
Improved staff competences
Rationalisation of legacy systems
Automation of business processes help in decrease the number of staff needed to operate P3O ® services.
8
Benefits of Project Management
The main benefit of project management is to help you to maintain your projects efficiently, letting you solve issues more quickly. It needs time and money to maintain & manage a project, but the following good practices can help you:
Increase your possibilities of accomplishing the desired result
Get an updated perspective on your project, and how it suits your business strategy
Prioritise the resources of your business and make sure their effective use
Establish the scope, schedule and budget accurately from the beginning
Stay on schedule and keep costs and resources to budget
Enhance productivity and quality of work
Support consistent communications amongst staff, suppliers and clients
Meet the various needs of the project’s stakeholders
Decrease risks of a project failing
Improve customer satisfaction
Gain a competitive advantage and boost your bottom line
Reduction in project overhead and elimination of heavy process for its own sake
More efficient management of company resources: Human, Technical and Financial
9
Multiple Choice Questions 1:
1. Which of the following is NOT a way in which tools can be used?a. Collaborativeb. Individualc. Communityd. Integrated
2. Which among the below tool provides integrated reports for multiple users froma single set of data?a. Complex modellingb. Benefit realisationc. Integrated modellingd. Enterprise PPM solutions
3. A coordinated set of strategic processes and decisions that commonly
allow the most efficient balance of organisational change and business
as usual/operations is referred to as
a. Project Management
b. Portfolio Management
c. Programme Management
d. Strategic Management
4. What all is included in a P3O ® model?i. Portfolioii. Programmeiii. Planningiv. Project Office
a. i, ii and ivb. ii, iii and ivc. i, iii and ivd. All of these
10
5. Some of the important documents connected with a well‐managed programme are:
a. Programme Mandate b. Programme Brief c. Programme Report d. Programme Definition
11
Strategic Objectives
Business as Usual: “The way business normally achieves its objectives”.
Project vs. Business‐As‐Usual
Projects Business‐As‐Usual
Projects are temporary, unique and
complex
Business‐As‐Usual changes to an existing
product
To Address a problem, opportunity or
change
Maintenance and continual improvements
Requires specific governance and
management
Managed within existing organisation
12
In Projects
• Governance: (e.g. Business Case)
• Maintenance: (e.g. Planning and Control)
• Delivery: (e.g. Solution Delivery)
In Business‐As‐Usual
Existing Product
New Requirements
Updated Product
13
What are P3O ®s?
A decision‐enabling and support business model for all business change within an
organisation. This will include single or multiple physical or virtual structures, i.e.
offices (permanent and temporary), providing a mix of central and localised functions
and services, and integration with governance arrangements and the wider business
such as other corporate support functions.
Simply implementing a P3O ® model will not provide effective change governance
support. It is the maturity that makes a difference. A mature P3O ® may have been in
existence for many years and be well established, typically mature processes, trained
experienced staff and senior management commitment. A key attribute is a high
morale amongst mature P3O ®’s. Organisations with low maturity in P3RM stand
much to gain from an excellent P3O ® model.
Cost Model
The business case should cover both set‐up and ongoing costs
Temporary offices: set up and operational costs that support individual
programmes or projects are included in the business case. Expenditure will
follow the financial rules set up by the programme or project
Permanent offices: varies cost models may be available and will be based on
estimated usage levels and metrics are designed to determine the proportion of
cost associated with each service
Example of some metrics: Financial value, number of programmes and projects,
delivery resource numbers used, weighting against historic business benefits
achieved
The following are the elements of P3O ® model:
14
Organisation Portfolio Office: Permanent office set up support the definition
and delivery of a portfolio of change across the entire organisation or
enterprise.
Hub Portfolio Office: Permanent office set up to support the definition and
delivery of a portfolio of programmes and projects within a department,
division, geographical region or business unit.
Programme Office: Temporary office set up to support delivery of a specific
change initiative being delivered as a programme.
Project Office: Temporary office set up to support delivery of a specific
change initiative being delivered as a project.
15
Centre of Excellence: A portfolio, programme and project management
standards unit, which defines standards (process, templates and tools) skills
and training, manage knowledge and may provide independent assurance.
The COE may be part of a Portfolio Office or exist as a separate stand‐alone
unit.
16
Portfolio, Programme and Project Lifecycles
1. Understand: It is the first step, and it gives that fundamental knowledge of what
the portfolio should be accomplishing. It concentrates on explaining the scope of
the portfolio (helpful for when an organisation has more than one portfolio). It can
also involve knowledge of any current change actions which could set into this
portfolio. After that, work doesn’t stop because there is not a portfolio to drop the
projects into, so there will likely be some projects or programmes ongoing that can
be incorporated into the portfolio.
2. Categorise: It is challenging to maintain various change actions in a big
organisation, so projects and programmes should be categorised. You can then see
if anyone area is lacking investment. The categorisation is done on any criteria that
accommodate your business, and you can even set up sub‐portfolios.
3. Prioritise: Prioritisation is essential. It is necessary to prioritise the actions within the portfolio so that the projects and programmes with the most useful return and
the good connection to strategy are at the top. These then get the project
resources and investment first, so the company obtains the benefits. It is beneficial
to have a structured prioritisation system.
4. Balance: The portfolio must be balanced. Through it, the direction means that it
should make reasonable sense in terms of timing, risk (not too many high‐risk
projects happening at the same time), and resources (ensuring there are resources
17
to do everything; not spending a year doing Finance projects only to leave all the
Marketing ones to next year).
5. Plan: It is essentially the tasks & actions that the project, programme and portfolio
managers will do. The plan is to design a portfolio strategy for that portfolio and to
put together a delivery plan. Then this can be published widely, and the executives
can publicly announce their help and support for it and work can start.
Portfolio Delivery Cycle
The portfolio delivery cycle involves seven practices. These are created to deliver the
portfolio work and keep the portfolio itself up to date as things change, just like a
leader guides and manages an organisation.
Management Control: Once agreed, the portfolio strategy and delivery plan
form the baseline for what is to be delivered. The purpose of the management
control practice is to ensure that progress, at an individual and portfolio level, is
regularly monitored against this baseline. This helps to ensure that delivery
stays on track and that the portfolio remains strategically aligned.
Benefits Management: Benefits management is also a component of
programme management and project management. It is important to identify
at a portfolio level and maintain the benefits from all the change initiatives,
projects and business‐as‐usual work. Benefits management is a well‐organised
strategy for increasing good business results for an organisation as an outcome
of change. It is vital to efficient programme and project management and
successful delivery.
Financial Management: Portfolios can take a lot of money. It is the combined
cost of all the projects supporting the strategic goals, which can total hundreds
of thousands, if not millions, of dollars. So strong financial management is
necessary. There is also a role here in making sure that the company’s fiscal
year and management cycle ties up with the decision making about the
portfolio so that you don’t end up with lots of mid‐year reporting to do at the
most critical part of the delivery or end up missing the deadlines for budget
submissions because you didn’t know about them.
18
The goal of the financial management practice is to assure that the portfolio
management processes and decisions are aligned to the financial management
cycle and that financial concerns form a fundamental part in all decisions
regarding the services and ongoing viability of change initiatives, both at an
individual and a collective level.
Risk Management: A risk management strategy gives a structured and
consistent approach to identifying, assessing and managing risk. A risk
management strategy can be generated and executed by also the smallest of
groups or projects or built into a complicated strategy for a multi‐site
international organisation.
As you perform risk management on projects and programmes, you also have to
do it at a portfolio level. It is the same basic strategy, but at this level it looks at
consolidated risk and personal risks to individual change initiatives.
Stakeholder Engagement: A Stakeholder Engagement Strategy is a
procedure to interact with project stakeholders to obtain their help for the
project. It includes:
o Stakeholder list o Project phase o Contact name(s)
o Areas of Influence o Power o Engagement approach
Organisational Governance: Governance is a different part that develops
over projects, programmes and portfolios. At this level, it is necessary to
ensure that governance of the portfolio is aligned to the overall corporate
governance strategy, so it all ties up. Basically, it is only about to ensure that
there is transparency and clarity about decisions and data.
19
Resource Management Strategy: Portfolios have dedicated resources and
the project and programme managers delivering the change actions and
projects. Resource management includes assuring that there are enough
people with the appropriate skills to deliver the change in the most suitable
schedules.
If you think about the number of resources included in a portfolio, this can
be a lot of people, so the overhead in getting their availability and making
sure that people are scheduled appropriately can be huge. At some level, the
amount of resources available to deliver change initiatives is constrained.
The purpose of the resource management the practice is to put in place
mechanisms to understand and manage the number of resources available
and required. This strategy describes how a resource to be consumed by the
programme. Finances, people, systems, accommodation, facilities, and
specialisms will all be covered by this strategy.
Assessing the current state of P3O ® provision is a key activity of the identify
process in the permanent P3O ® lifecycle.
20
Quality Assurance
Quality Assurance is the collection of systematic activities designed to make sure that
the goals and management processes of a project, programme or portfolio are fit for
purpose. P3O ® assurance is the method of giving confidence to stakeholders that
projects, programmes and portfolios will accomplish their scope, time, cost and
quality goals, and realise their benefits.
The objectives of assurance are to:
Review management planning Monitor effectiveness of functions and processes Give stakeholders confidence that the Work is Being Managed Effectively and
Efficiently
The sponsor is responsible for P3O ® assurance, which varies from quality assurance in that it is performed within the P3O ® organisation. It must be independent of those directly included in the delivery of work. This independence can be accomplished in several methods including, for example, using individuals external to the delivery team, or merely by regular and formal reporting of agreed information in a manner that cannot be influenced by the delivery team. Assurance makes recommendations but not decisions, although it forms a sound basis upon which decisions are taken.
Quality Assurance will usually be risk‐based, with the riskiest phases of the work being directed to the most definite assurance processes. Therefore, the term ‘risk’ associates with the management environment, rather than the delivery risks that would appear in a P3O ® risk register. More complex projects, programmes and portfolios typically require a set of assurance processes. It assures that all perspectives are suitably covered, e.g. safety, regulative compliance, governance processes.
In specific environments, various assurance providers may be required, each of which will have their own methods and specified scope intended to satisfy the requirements of one group of stakeholders. The total assurance responsibility can become responsible for these parameters.
21
Quality Assurance resources will come from the support function, provided that they are independent of the delivery of the project, programme or portfolio. It is the responsibility of the sponsor to utilise the outcomes of the assurance process to recognise any failings in the project's management and instil confidence in the project amongst its stakeholders.
Project
The assurance reviews and audits where the project is part of a programme or portfolio, the assurance reviews and audits will be conducted by the programme or portfolio support function. Where the project is stand‐alone, the sponsor must secure resources from outside the project to provide assurance.
Programme
Within a programme, there are two levels of assurance: assurance of the projects and benefits realisation activities; and assurance of the programme management process.
The programme manager usually fulfils the role of sponsor for the component projects and, in this position, has responsibility for project assurance, while remaining independent from programme assurance. This will require the programme sponsor to plan assurance using separate resources for the project and programme‐level assurance.
Portfolio
In the portfolio level, arrangements within projects and programmes interface with the host organisation’s assurance function. The host organisation will typically have mandated assurance functions. It is the responsibility of those in charge of these business‐wide functions to ensure that the business has the assurance it needs.
Portfolio assurance requires to flow to the board of the organisation as it gives a critical link between assurance and organisational governance. Usually, the audit committee of organisation has a general responsibility for ensuring that the board has the assurance that it requires. The audit committee, therefore, has a key assurance role to play within portfolio management.
22
Multiple Choice Questions 2:
1. Hub Portfolio Office is defined as
a. Permanent office set up support the definition and delivery of a portfolio of
change across the entire organisation or enterprise.
b. Permanent office set up to support the definition and delivery of a portfolio
of programmes and projects within a department, division, geographical
region or business unit.
c. Temporary office set up to support delivery of a specific change initiative
being delivered as a programme.
d. Temporary office set up to support delivery of a specific change initiative
being delivered as a project.
2. ______is the method of giving confidence to stakeholders that projects,
programmes and portfolios will accomplish their scope, time, cost and quality
goals, and realise their benefits.
a. Stakeholder Engagement
b. P3O ® Assurance
c. Cost Management
d. Stakeholder Management
3. Which of the following statements are true about projects?
a. Are temporary, unique and complex
b. To address a problem, opportunity or change
c. Requires specific governance and management
d. All of these
4. Which of the following is a key activity of the identify process in the permanent
P3O ® lifecycle?
a. Assessing the current state of P3O ® provision
b. Planning delivery tranches
c. Delivery of new capability
d. None of these
5. Which of the following is NOT a part of portfolio delivery lifecycle?
23
a. Risk Management
b. Organisational governance
c. Prioritisation
d. Management Control
24
Key Performance Indicators
As a minimum, improvements targets and associated KPIs should be set for the
following areas:
Overall programme and project success rates in relation to capital cost,
duration, operating cost, and benefits realisation for each portfolio
Improved portfolio balance – in terms of overall risk, programme and
project lifecycle stages, strategic alignment, and investment type
Enhance contribution to strategic objectives
Maturity Levels
The maturity levels allow organisations to identify a growth pathway by which they
may decide to progress. This process should be seen as a long‐term strategic
commitment rather than a quick‐fix for immediate tactical problems. Short‐term
improvements can be targeted to accomplish specific objectives; the real benefits
come through continual process improvement.
P3M3 uses a five‐level maturity framework and five Maturity Levels are:
Level 1 – awareness of process
Level 2 – repeatable process
Level 3 – defined process
Level 4 – managed process
Level 5 – optimised process
These levels are consistent with the original P3M3 model and its predecessor, the
Project Management Maturity Model.
The five‐level hierarchy of P3M3 does not mean that every organisation should aim
for or should achieve, Level 5 in all three models. Each organisation should decide
which maturity level would be best for its specific business requirements at a given
time.
25
1. Level: Awareness of process
Processes are not usually documented. There are no, or only a few, process
descriptions. They will generally be acknowledged, in that managers may have
some recognition of the necessary activities, but their actual practice is determined
by events or individual preferences and is highly subjective and variable. Processes
are therefore undeveloped, although there may be a general commitment to
process development in the future.
Incomplete processes mean that the required activities for better practice are
either not performed at all or are only partially completed. There will be little, if
any, guidance or supporting documentation and even terminology may not be
standardised across the organisation. Top management should be aware of the
requirement to use a process‐based approach to P3M and have committed to
improving it but may lack sufficient engagement.
Level 1 organisations may have achieved a number of successful initiatives, but
these are often based on key individuals’ competencies rather than organisation‐
wide knowledge and capability. In addition, such ‘successes’ are often achieved
with a budget and/or schedule overruns and, due to the lack of formality, Level 1
organisations often over‐commit themselves, abandon processes during a crisis,
and are unable to repeat past successes consistently. There are very little planning
and executive buy‐in, and process acceptance is limited.
2. Level: Repeatable Process
Top management will be taking the lead on a number of the initiatives, but there
may be inconsistency in the levels of engagement and performance. The
organisation will be able to demonstrate, by reference to specific programmes or
projects, that basic management practices have been established and that
processes are developing. Some key individuals can show a successful track record
and, through them, the organisation is capable of repeating earlier successes on
similar programmes and projects in the future.
Process discipline is unlikely to be accurate, but where it does exist, programmes
and projects are performed and managed according to their documented plans.
Project status and delivery will be visible to management at defined points, such as
on reaching significant milestones.
26
Level 2 is also accomplished if the organisation has defined the approach but it hasn’t
yet been universally deployed or adopted, so it is on the way to Level 3. There is still a
significant risk of exceeding cost and time estimates. Key factors that may have
preconditioned the organisation to experience difficulties or failure include:
Inadequate measures of success
Unclear responsibilities for achievement
Ambiguity and inconsistency in business objectives
Lack of a fully integrated risk management process
Limited experience in change management
Inadequacies in communications strategy
3. Level: Defined Process
The management and technical processes necessary to achieve the organisational
purpose will be documented, standardised and integrated to some extent with other
business processes. There is likely to be process ownership and an established process
group with responsibility for maintaining consistency and process improvements
across the organisation. Such improvements will be planned and controlled, perhaps
based on assessments, with planned development and suitable resources being
committed to ensuring that they are coordinated across the organisation.
Top management is engaged consistently and provide active and informed support. A
critical distinction between Levels 2 and 3 is the scope of standards, process
descriptions and procedures. These standard processes can be tailored within
programmes and projects to suit specific circumstances, but these will be by tailoring
guidelines.
4. Level: Managed Process
Level 4 is characterised by behaviour and processes that are quantitatively managed.
There will be evidence of quantitative objectives for quality and process performance,
and these will be used as criteria in managing processes. The measurement data
collected will contribute towards the organisation’s overall performance
measurement framework and will be imperative in analysing the portfolio and
ascertaining the current capacity and capability constraints. Top management will be
committed, engaged and proactively seeking innovative ways to achieve goals.
27
Using process metrics, management can effectively control processes and identify
ways to adjust and adapt them to particular projects without loss of quality.
Organisations will also benefit through improved predictability of process
performance.
5. Level: Optimised Process
The organisation will focus on the optimisation of its quantitatively managed
processes to take into account predicted business needs and external factors. It will
anticipate future capacity demands and capability requirements to meet delivery
challenges. Top managers are seen as exemplars, reinforcing the need and potential
for capability and performance improvement.
It will be a learning organisation, propagating into other programmes and projects the
lessons learned from past reviews. The organisation’s ability to rapidly respond to
changes and opportunities will be enhanced by identifying ways to accelerate and
share learning.
The organisation will be able to show that continual process improvement is being
enabled by quantitative feedback from its embedded processes and from validating
innovative ideas and technologies. There will be a robust framework addressing issues
of performance management.
The organisation will be able to demonstrate strong alignment of organisational
objectives with business plans, and this will be cascaded down through scoping,
sponsorship, commitment, planning, resource allocation, risk management and
benefits realisation.
Principles for Extracting Value
a. Govern effectively
• Supporting SROs & Senior Management.
• Ensuring issues, risks & changes escalated to right level
• Providing independent Gate Review coordination & assurance
• Collecting complete, timely & accurate data
• Amalgamating & analysing data to enable quality decision making
b. Hold people to account
Providing standard role descriptions & terms of reference for boards
Providing support, coaching & training for all levels of role
Providing decision support to Senior Mgt. (analysis of options & consequences)
28
Ensuring right decisions escalated to the right people
c. Prioritise investment, align, and adjust to business strategy
Providing decision support to Senior Management (analysis of options &
consequences)
Maintaining portfolio register of all programmes & projects (including ideas in
‘the pipeline’)
facilitating & supporting pre‐programme & pre‐project scoping workshops
Providing ‘fast‐track’ mobilisation service ensuring scope & plans are aligned to
strategic & BAU priorities
Maintaining awareness of upcoming strategy changes, business issues, delayed
decisions and their impact.
d. Safeguard value
Supporting the Business Case process
Providing benefits tracking service to programmes & projects
Ensuring a robust & useable measurement process
Ensuring benefits are not double‐counted
e. Invest in people and process
Developing tailored approaches based on OGC guidance
Developing training, coaching & mentoring approaches for all P3RM roles
Advising on skills & capability assessments and training plans (using OGC P3RM
Skills model)
f. Track progress through highlight and exception‐based reporting
Providing reporting & exception management service for all levels
Developing management dashboards
Ensuring data collection processes operate correctly
29
Multiple Choice Questions 3
1. A P3O ® model provides
a. Replacement of programme and project boards
b. Decision making model of the organisation
c. A decision‐enabling or delivery support structure for all change within an
organisation
d. All of these
2. Business‐as‐usual is defined as
a. The integration of the concepts: run the business and change the business into
portfolio
b. The method by which the business normally achieve its objectives
c. An organisation's overall collection of programmes and projects
d. None of these
3. Which of the following benefit of implementing standard tools and techniques is
MOST likely to decrease the number of staff needed to operate P3O ® services?
a. Automation of business processes
b. Improved compliance with business processes
c. Improved timeliness of decision‐support information
d. Improved quality of decision‐support information
4. P3M3 uses a five‐level maturity framework. Which of the following is second level
of maturity?
a. Optimised Process
b. Repeatable process
c. Defined process
d. Managed process
5. Which of the following terms is used to allow organisations to identify a growth
pathway by which they may decide to progress.
a. Short term improvements
b. Long term improvements
c. Maturity levels
d. Improvement levels
30