Which is NOT a functional role?
Answer : C
The P3O Foundation (2013) manual lists Benefits and Value, Information Management, and Planning as functional roles, but Project Officer is not. Section 3.5.1 states, 'Functional roles within a P3O include Benefits and Value, Information Management, and Planning, each providing specialized support.' The Project Officer (C) is a delivery support role, not a functional one, as it focuses on execution (Section 3.5.6). The 2013 edition distinguishes these roles to clarify P3O's structure, ensuring functional roles drive strategy and support, while delivery roles handle operations. This delineation enhances organizational clarity.
Which of the following are recommended for the implementation of a P3O model?
1. Follow a recognized programme or project methodology
2. Define a budget and associated timescales to deliver
3. Appoint a P3O Sponsor
4. Use a programme approach to implement a single office P3O staffed by one individual
Answer : A
The P3O Foundation (2013) manual recommends following a recognized methodology, defining a budget and timescales, and appointing a P3O Sponsor for implementation. Section 4.2.1 states, 'Implementation should follow a recognized programme or project methodology, include a defined budget and timescales, and involve appointing a P3O Sponsor to provide leadership.' However, using a programme approach for a single-office P3O staffed by one individual (4) is not recommended due to scalability and governance issues. The 2013 edition emphasizes a structured approach to ensure success, with the Sponsor driving strategic alignment and methodology providing a framework. Options B, C, and D include the impractical fourth element, making A the correct choice for a robust implementation process.
Which of the following statements about the return of internal resources to an operational role when closing a temporary Programme Office are true?
1. Feedback to the line manager should be given on performance
2. Staff members will be reluctant to return if they are to lose status
Answer : C
The P3O Foundation (2013) manual confirms both statements are true regarding resource return from a temporary Programme Office. Section 4.4.4 states, 'Feedback on performance should be provided to line managers to support staff development,' and 'Staff may be reluctant to return if they perceive a loss of status or responsibility.' The 2013 edition acknowledges these human resource dynamics, emphasizing the need for performance feedback to aid reintegration and recognizing status loss as a barrier. Options A, B, and D are incorrect as both factors are relevant, ensuring smooth transition and morale management during closure.
Which is NOT a way that tools are typically used?
Answer : B
The P3O Foundation (2013) manual identifies integrated, collaborative, and individual as typical ways tools are used, but not 'connected' as a distinct category. Section 6.2.1 states, 'Tools are typically used in an integrated manner across functions, collaboratively by teams, or individually by single users, depending on organizational maturity.' The term 'connected' (B) is not defined as a usage mode; it may imply a technical link but lacks specific application in the P3O context. The 2013 edition focuses on these three usage patterns to align with P3M3 maturity levels, ensuring tools support PPM effectively. Options A, C, and D are explicitly recognized, making B the correct choice for an atypical use. This clarity aids in selecting appropriate tool strategies.
Which describes the focus of a Portfolio Office in relation to programmes?
Answer : D
The P3O Foundation (2013) manual describes the Portfolio Office's focus as ensuring investment in the right programmes. Section 5.3.2 states, 'The Portfolio Office focuses on ensuring that investment is directed toward the right programmes by aligning them with strategic objectives and optimizing the portfolio.' This differs from implementation (A), programme support (B), or standard definition (C), which are programme or COE roles. The 2013 edition emphasizes this strategic investment role to maximize value, supporting P3O's governance function. This ensures resource allocation aligns with organizational priorities.
How can a P3O directly support effective teamwork between Programme Managers located in different regions?
Answer : C
The P3O Foundation (2013) manual highlights that implementing standard collaborative tools directly supports effective teamwork among regionally dispersed Programme Managers. Section 6.2.2 states, 'Standard collaborative tools, such as information portals and shared workspaces, enable effective communication and coordination among distributed teams, including Programme Managers in different regions.' This contrasts with appointing regional sponsors (A), which is a governance role, portfolio prioritization (B), which focuses on strategy, and fast-track mobilization (D), which aids initiation. The 2013 edition emphasizes technology's role in overcoming geographical barriers, ensuring real-time collaboration and consistency. This approach enhances team cohesion and efficiency, aligning with P3O's support function for distributed models.
Where should an Organization Portfolio Office ultimately report?
Answer : A
The P3O Foundation (2013) manual specifies that the Organization Portfolio Office (OPO) should ultimately report to a main board director. Section 5.3.2 states, 'The Organization Portfolio Office should report to a main board director to ensure strategic alignment and direct accountability at the highest level.' This differs from corporate services (B), Programme Manager (C), or Head of P3O (D), which are lower or supportive levels. The 2013 edition emphasizes this reporting line to integrate portfolio oversight with corporate governance, ensuring strategic influence. This structure supports effective decision-making and resource allocation.