P3OF Practice Questions

The Organization Portfolio Office is a P3O model defined as a single, permanent office established at the corporate level. Its primary purpose is to support senior management's decision-making on strategic matters and to manage the organization's investment portfolio. This model provides a centralized overview of all change initiatives, ensuring they are aligned with strategic objectives and that portfolio-level support, such as strategic planning and dependency management, is consistently applied across the organization.

A. P3O model with Hub Portfolio Offices: This is not a single office model; it consists of a central hub office and multiple satellite (spoke) offices.

C. Virtual Office: This model is not a permanent, physical office but rather a decentralized structure where P3O functions are performed by individuals across the business.

D. Flexible resource pool: This is a function or service that a P3O may provide (managing skilled resources), not a structural P3O model itself.

AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). The Stationery Office.

Section 3.3.1

Organization Portfolio Office: "An Organization Portfolio Office is a single permanent office set up to support senior management to make strategic decisions..." (p. 26).

Section 3.3.2

Hub Portfolio Offices: Describes this model as a central hub with several permanent or temporary spoke P3Os (p. 27).

Section 3.3.3

Virtual P3O: "A virtual P3O model is not a physical office..." (p. 28).

Section 2.3.2

Centre of Excellence Functions: Lists 'Developing and managing a flexible resource pool' as a potential P3O function

not a model (p. 18).

A key function of a P3O is to provide assurance, which includes ensuring that projects and programmes comply with corporate standards and governance. Information assurance is a critical aspect of this. The P3O ensures that non-functional requirements, such as data security, are identified, assessed, and integrated into the project's scope and plans from the very beginning (i.e., during initiation). This proactive approach helps mitigate risks related to information security and ensures alignment with organizational policies, which is a core P3O assurance responsibility.

A. Escalating issues to senior management: This is a general P3O function for any significant risk or issue, not a role specific to information assurance.

B. Providing capacity planning for the portfolio: This is a resource management function within a P3O, focused on balancing resource supply and demand, not information assurance.

D. Booking for operational staff: This is an administrative or resource management task, which is unrelated to the strategic function of information assurance.

---

1. AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). The Stationery Office.

Section 3.4.2

Table 3.2 'P3O services': This table lists "Assurance" as a key P3O service. A specific activity under this service is "Ensuring that any corporate strategies (e.g. for information security

quality

health and safety) are reflected in the programme/project." This directly supports the P3O's role in ensuring security is assessed at the start.

Section 4.4.3 'Assurance': This section details the P3O's role in providing independent scrutiny and challenge. It states

"The P3O may be responsible for ensuring that appropriate assurance roles are appointed to a programme or project and that assurance activities are embedded in the programme/project lifecycle." This reinforces the concept of embedding security assessments from the beginning.

The Programme Manager is the primary 'customer' of the Programme Office, responsible for the successful delivery of the programme's outcomes. The Head of the Programme Office is responsible for managing the office's resources and ensuring it delivers the required support services effectively. Therefore, as a minimum, these two roles must collaborate to review the resourcing of the Programme Office while it is running. This ensures that the support provided remains aligned with the evolving needs of the programme, making the most efficient use of resources. This relationship represents the core service provider (Head of Programme Office) and customer (Programme Manager) dynamic.

A. Head of P3O and P3O Sponsor: These roles provide strategic oversight for the entire P3O model, not the specific operational resourcing of a single, running Programme Office.

C. P3O Sponsor and Portfolio Analyst: The P3O Sponsor is a high-level champion, and a Portfolio Analyst focuses on portfolio-wide data, not the direct management of a specific Programme Office.

D. Head of COE and Programme Specialist: A Head of a Centre of Excellence (COE) is specific to that P3O model, and a Programme Specialist is a resource within the office, not a management role responsible for review.

1. AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). The Stationery Office.

Appendix A

Section A.8 (Programme or Project Manager): This section establishes the Programme Manager as the "customer of the Programme or Project Office"

highlighting their direct interest in the adequacy of the office's services and resources.

Appendix A

Section A.6 (Programme Office Manager): This section outlines the key responsibilities

which include "Managing the resources of the Programme Office" and "Day-to-day management of the Programme Office". This confirms their direct responsibility for the topic in question.

Chapter 4

Section 4.4.2 (Temporary Office Roles): This section describes the typical structure of a temporary office supporting a specific programme

reinforcing the direct reporting and service relationship between the Programme Office Manager and the Programme Manager.

The P3O model distinguishes between the functional areas or services that a P3O provides and the specific job roles that deliver those services. 'Benefits and Value', 'Information Management', and 'Planning' are all core functional areas or services offered by a P3O to support decision-making and delivery. In contrast, a 'Project Officer' is a specific job title or role within the P3O structure. This role is responsible for performing tasks that contribute to the delivery of P3O functions but is not a functional area itself.

A. Benefits and Value: This is a key P3O functional area, focusing on the identification, tracking, and realization of benefits from investments in programmes and projects.

B. Information Management: This is a core P3O function that includes providing management information, dashboards, and knowledge management to support effective decision-making.

D. Planning: This is a fundamental P3O function, providing planning support, standards, and expertise to projects, programmes, and the portfolio.

1. AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). The Stationery Office.

Chapter 4

Section 4.3

Table 4.1: This table outlines the main P3O functions and services

which include activities related to Planning

Benefits Management

and Information Management (as part of Management Information and Knowledge Management).

Chapter 5

Section 5.4: This section details the generic P3O roles and responsibilities. Section 5.4.5 specifically describes the 'Programme or Project Officer' as a role

distinct from the functions listed in Chapter 4. This confirms that 'Project Officer' is a role

not a function.

A P3O provides various services to support an organization's investment in change. While challenging data, scrutinizing impacts, and escalating risks are core Portfolio, Programme, and Project Management (PPM) functions related to assurance and control, providing a secretariat service is fundamentally an administrative function. Although it is applied to PPM governance boards, the task itself is not a unique PPM discipline. A P3O often provides this service because it has the centralized skills and resources, which improves overall business efficiency by avoiding duplication of administrative roles across the organization.

A. Challenging project data is a core assurance and governance function within PPM, ensuring the quality of information for decision-making.

B. Scrutinising the impact of project delivery on business as usual is a key part of benefits realization and change management, which are integral to PPM.

C. Escalating risks and issues is a fundamental PPM process for governance and control that a P3O is established to facilitate.

1. AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). The Stationery Office.

Page 31

Table 4.1 - P3O Functions and Services: This table lists "Secretariat/administrative support for governance boards" as a service under the "Governance and control support" category. This distinguishes it as a support service

unlike the other options which are core PPM disciplines (e.g.

"Independent assurance

" "Issue and risk management support

" "Benefits management support") listed in the same table.

Section 4.3.2

Governance and control support: This section details the services

including secretariat support

which "ensures that the governance boards work effectively and efficiently." This highlights its role in efficiency

separate from the core technical PPM disciplines.

A core purpose of a P3O is to provide delivery support to projects, programmes, and portfolios. Reporting portfolio performance through management dashboards is a fundamental delivery support service. It falls under the 'Management Information and Reporting' function, which enables effective governance and decision-making by providing a clear, consolidated view of progress, risks, and issues. This information is crucial for senior management to steer the portfolio and ensure successful delivery of strategic objectives. This service acts as the 'single source of the truth' for performance data.

B. Train and coach PPM staff: This is a Centre of Excellence (CoE) function focused on developing organizational capability and competency, rather than providing direct support to in-flight delivery activities.

C. Provide a flexible resource pool: This is a strategic resource management function. While it supports delivery, reporting is a more universal and fundamental information-based delivery support service found in all P3O models.

D. Develop standard processes for producing Business Cases: This is a Centre of Excellence (CoE) function. It involves creating standards, methods, and templates to ensure consistency, not direct support for project execution.

AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). TSO (The Stationery Office).

Chapter 2

Section 2.4.2

Delivery Support Functions: This section lists "Tracking and reporting" and "Information management" as key delivery support functions. Management dashboards are a primary tool for these functions.

Chapter 2

Table 2.1

P3O functions and services: This table explicitly lists "Management dashboards" as a service under the "Governance

Accountability and Scrutiny" and "Management Information (MI) and Reporting" functions. In contrast

it lists "Development of standards and methods" and "Training and development" under the "Consultancy and Centre of Excellence" function

confirming options B and D are incorrect.

The permanent P3O model lifecycle begins with the 'Define' process. This process is composed of two sequential steps: 'Identify' and 'Define'. The initial 'Identify' step focuses on understanding the current organizational context, including its maturity, challenges, and stakeholder perspectives. Activity A, understanding stakeholder views, is a core part of this initial 'Identify' step. The information gathered is then used as an input to the second step, 'Define', where the vision (Activity B) is created. Therefore, understanding the current stakeholder view is the first activity undertaken in the 'Define' process.

B. Creating a vision occurs during the second step ('Define') of the 'Define' process, and it uses the information gathered during the initial 'Identify' step.

C. Determining detailed processes is part of developing the P3O Blueprint, which happens later in the 'Define' process, after the vision has been established.

D. Delivering the P3O capability is the primary purpose of the 'Deliver' process, which follows the completion of the entire 'Define' process.

1. AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). TSO (The Stationery Office).

Section 8.3

Figure 8.1 'The P3O Implementation Lifecycle': This figure clearly shows the 'Define' process is the first stage and is comprised of two steps: 'Identify' followed by 'Define'.

Section 8.4.1 'Step 1: Identify': This section details the first step of the 'Define' process

stating its purpose is to "understand the current organization... and the key stakeholders." This directly supports option A as an initial activity.

Section 8.4.2 'Step 2: Define': This section states

"The purpose of this step is to take the information gathered in the Identify step and use it to create a Vision...". This confirms that creating the vision (Option B) occurs after the activities in the 'Identify' step (Option A).

The 'Identify' process is the first stage in the portfolio management lifecycle. Its purpose is to capture all potential and ongoing change initiatives (programmes and projects) across the organization. A key activity within this process is to document an initial justification for each proposed initiative to enable a high-level assessment. This is typically achieved by creating an outline or brief Business Case, which captures the core idea, strategic alignment, and expected benefits without requiring extensive detail at this early stage.

A. Refine the Vision Statement: Refining the Vision Statement is a strategic management activity that provides the context for the portfolio; it is an input to the 'Identify' process, not an activity within it.

C. Plan tranches of delivery: This is a detailed programme management planning activity that occurs after a programme has been identified, prioritized, and approved for initiation, not during the initial 'Identify' phase.

D. Deliver the new capability: This is an execution activity performed during the project and programme delivery lifecycle. The 'Identify' process is concerned with deciding what to do, not the actual delivery.

AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). TSO (The Stationery Office).

Section 6.3.1

Identify process: "The purpose of the Identify process is to collate a list of all the programmes and projects that are to be managed through the portfolio... The information required at this stage should be minimal

e.g. an outline Business Case..." (p. 56). This directly supports option B as a core activity.

Figure 6.2

The Portfolio Management cycle: This figure illustrates that 'Identify' is the first step

focused on capturing initiatives

which precedes detailed planning ('Plan') and delivery. This context shows why options C and D are incorrect as they occur later in the overall lifecycle.

Section 6.2

Prerequisites for Portfolio Management: This section explains that a clear vision and strategic objectives must be in place before the portfolio management cycle begins

confirming that refining the vision (Option A) is a prerequisite

not part of the 'Identify' process. (p. 55).

A P3O (Portfolio, Programme, and Project Office) model is explicitly defined as the decision-enabling and delivery-support business model for all business change within an organization. Its primary purpose is to provide a structured framework that enables senior management to make informed strategic decisions about their portfolio of projects and programmes. It ensures that the right initiatives are undertaken and are delivered correctly by providing standardized processes, support, and guidance. This central model integrates governance with the delivery mechanisms for change.

A. Programme: A programme is a temporary structure designed to manage a group of related projects to deliver specific outcomes and benefits, not the overarching support model for all organizational change.

C. Project: A project is a temporary endeavor created to deliver a specific output or product. It is a component of change, not the business model that supports all change.

D. Portfolio: A portfolio is the collection of all projects and programmes an organization is undertaking to achieve its strategic objectives. The P3O model supports the management of this portfolio.

1. AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). The Stationery Office (TSO).

Correct Answer & Explanation: Section 1.1

"What is P3O?"

Page 5

Paragraph 1. The text states

"A Portfolio

Programme and Project Office (P3O) model is the decision-enabling and delivery-support business model for all business change within an organization."

Incorrect Options: Section 2.2.1

"Portfolio

programme and project management"

Page 12

Figure 2.1. This figure provides the official definitions for Portfolio

Programme

and Project

distinguishing them from the P3O model itself.

The closure of the P3O implementation programme signifies that the P3O model has been successfully established and is now fully operational. The temporary programme structure set up to create the P3O is no longer needed because the P3O's functions, services, and processes are now integrated into the organization's standard operating procedures. This transition from a temporary implementation effort to a permanent, self-sustaining business function is known as becoming 'business as usual' (BAU). The programme's closure is the formal milestone marking this successful transition.

A. The Vision Statement is created during the initial stages of the implementation programme to define the end-goal and guide the delivery, not rewritten at the end.

B. The Blueprint is a detailed model of the future P3O, developed during the definition and delivery phases of the implementation, not produced upon its closure.

C. Risks to the implementation are identified, assessed, and managed continuously throughout the entire lifecycle of the implementation programme, not just captured at the end.

AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). The Stationery Office.

Section 9.4.4

Tranche 3 and beyond – embed P3O as Business as Usual (BAU): This section explicitly discusses the final phase of implementation where the P3O becomes a permanent

self-sustaining business function. The closure of the implementation programme is contingent on this state being achieved.

Figure 9.2

The P3O Implementation Lifecycle: This diagram illustrates that the final stage of the lifecycle

following delivery

is the embedding of the P3O as Business as Usual

after which the implementation programme can close.

Section 9.2

The P3O Implementation Programme: This section describes the implementation as a temporary programme designed to deliver a permanent capability. The closure of this temporary structure happens once the capability is delivered and operational.