Free PRINCE2-FOUNDATION Practice Test

Effective issue management for changes to baselined products, including management products, is integrated with configuration management. When a request for change is approved, the relevant management product must be updated. To maintain an audit trail and ensure all stakeholders are using the correct version, the updated document is saved as a new version. This is a fundamental practice for controlling project documentation and preventing confusion or errors arising from using outdated information.

A. Changing the approach based on lessons is about process improvement, not the direct handling of a specific change to a product.
C. A change budget is typically established to fund approved changes to the project's specialist products, not administrative changes to management documents.
D. An off-specification is a type of issue where a product fails to meet its requirements. A request to change a management product is a 'request for change' issue type.

AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Section 14.2, "Issue and change control procedure"; Section 14.3.1, "Configuration management"; Appendix A.7, "Configuration item record".

PRINCE2 defines six aspects of project performance that must be managed to ensure the project is successful. These are costs, timescales, quality, scope, sustainability, and benefits. Tolerances are set for each of these aspects to enable management by exception. 'Timescales' is one of these six core performance metrics, focusing on whether the project is on schedule to meet its deadlines. The project manager monitors performance against these targets and escalates any forecast deviation beyond tolerance.

A. Efficiency: This is a general business metric and a potential benefit, but not one of the six specific performance aspects defined by PRINCE2.
C. Estimate: Estimates are used to forecast performance (e.g., cost and time), but 'estimate' itself is not a performance aspect to be managed.
D. Work: This is too general; 'scope' is the specific PRINCE2 performance aspect that defines the products and work required.

- AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Section 4.2.4, p. 34.

- AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Section 10.1, p. 108.

A primary benefit of PRINCE2 is its universal applicability. It is a generic framework, not tied to a specific industry or technology. This allows it to be applied to any type of project, regardless of its scale, complexity, geographical location, or culture. The method is designed to be tailored to suit the specific needs of any project environment.

A. PRINCE2 is a project management method. It is specifically designed for managing the unique, temporary nature of projects, not ongoing 'business as usual' activities.
B. Tailoring involves adapting the method appropriately; it does not mean leaving out core elements like principles, which would invalidate its use as a PRINCE2 project.
D. PRINCE2 provides a clear governance structure that requires and facilitates engagement with corporate or programme management, it does not avoid it.

1. AXELOS. (2023). Managing Successful Projects with PRINCE2® (7th ed.). PeopleCert. Chapter 1, Section 1.4, "PRINCE2 is a generic best practice framework that can be applied to any type of project."

PRINCE2 is founded on a customer/supplier environment. A fundamental assumption in this context is that the customer's role is to specify the desired result or outcome of the project. The customer defines the 'what' (the project's objectives and products) and provides the justification (the business case) and funding. The supplier's role is to provide the resources and skills to deliver this specified result, defining the 'how'. This clear separation of interests is a key concept that underpins the PRINCE2 organizational structure and processes.

A. The customer, not the supplier, is typically responsible for paying for the project as they are the ones who will receive the benefits.
B. The supplier, not the customer, is responsible for providing the resources (people, equipment) to create and deliver the project's products.
D. Tailoring is a project-wide responsibility led by the project manager and approved by the project board, which includes both customer and supplier representatives.

1. AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Section 2.2, "What PRINCE2 is," describes the customer/supplier context, stating the customer specifies the desired outcome.

2. AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Section 10.2, "The project management team," defines the roles, where the executive represents the customer's interests and the senior supplier represents the supplier's interests.

A key advantage of the 'manage by stages' principle is that it provides formal decision points for the project board. At the end of each management stage, the project board assesses the project's performance, the viability of the business case, and the plan for the next stage. This allows the board to decide whether to authorize the next stage, implement corrective action, or stop the project. These control points ensure the project does not proceed without senior management agreement at key intervals, preventing it from continuing in an uncontrolled manner.

A. The ability to use PRINCE2 for any project type is primarily an advantage of the 'tailor to suit the project' principle.
B. Aligning benefits with strategic objectives is a function of the business case theme and the 'continued business justification' principle.
D. Defining tolerances for delegated authority is a direct application of the 'manage by exception' principle, not 'manage by stages'.

AXELOS, "Managing Successful Projects with PRINCE2 7," 7th ed., 2023, Section 4.4: Principle: Manage by stages, p. 26.

AXELOS, "Managing Successful Projects with PRINCE2 7," 7th ed., 2023, Section 12.1: Purpose of the organization theme, p. 110 (describes the project board's decision-making role).

PRINCE2 specifies minimum requirements for applying each theme to ensure a project is genuinely being managed using PRINCE2. For the quality theme, one of the four minimum requirements is to "use lessons to inform quality planning, the definition of quality requirements, and quality control." This ensures that the project learns from previous experience to improve its quality management practices and deliverables.

B. The minimum requirement is to define a quality management approach, not necessarily use a prescribed one. The approach must be tailored to the project.
C. Using external standards is a valid approach but not a mandatory minimum requirement; quality standards can be defined internally if appropriate.
D. User stories are a technique often used in agile environments to define requirements, but their use is not a minimum requirement for the PRINCE2 quality theme.

- AXELOS. (2023). Managing Successful Projects with PRINCE2 7. Section 8.2 (The PRINCE2 minimum requirements for the quality theme), p. 82.

- AXELOS. (2023). Managing Successful Projects with PRINCE2 7. Table 8.1 (Responsibilities relevant to the quality theme), p. 83.

The project manager is granted authority by the project board to run the project on a day-to-day basis within the constraints laid out by them. This role is focused on the operational management of the project, ensuring it produces the required products within the specified tolerances for time, cost, quality, scope, sustainability, and benefits. The project manager's primary responsibility is to the project board.

A. The project board is responsible for the ultimate success of the project, not its day-to-day management, which they delegate.
B. The project manager is accountable to the project board; team managers are responsible for delivering work packages.
D. The project manager delegates work, but the overall responsibility for day-to-day management is assigned to them, not decided by them.

1. AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). PeopleCert. Section 7.3.5, p. 72. "The project manager is responsible for the day-to-day management of the project."

2. AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). PeopleCert. Figure 7.2, p. 67. (Shows the project manager's position below the project board, managing the project level).

The purpose of the ‘managing product delivery’ process is to control the link between the project manager and the team manager. This is achieved by the project manager issuing formal requirements for the work in a work package. The team manager then accepts this work package, formally agreeing to the requirements for how the work should be undertaken, including constraints, quality criteria, and reporting arrangements, before executing the work and delivering the products.

B. Highlight reports are created by the project manager for the project board during the ‘controlling a stage’ process, not by the team manager in ‘managing product delivery’.
C. The team manager, not the project manager, is responsible for producing a team plan if one is required. The project manager monitors progress against the stage plan.
D. The project manager escalates issues and risks that are forecast to exceed stage tolerance to the project board. This occurs within the ‘controlling a stage’ process.

- AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Chapter 19, "Managing product delivery process," p. 223.

- AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Figure 19.1, "Managing product delivery context," p. 224.

- AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Section 17.4.4, "Report highlights," p. 208.

The PRINCE2 methodology specifies minimum requirements for applying each theme to ensure a project is genuinely being managed using PRINCE2. For the 'change' theme, one of these minimum requirements is to define the project's approach to issue management. This definition must include establishing an issue management procedure and specifying the format and contents of the issue register. This ensures that all issues are captured, assessed, and managed in a consistent and controlled manner throughout the project lifecycle.

A. Protecting products is part of configuration management, but the minimum requirement is to define the approach, not specify every detail within it.
C. Producing issue reports is an activity within the defined procedure, but the minimum requirement is to define the procedure itself, not mandate every output.
D. Delegating change authority is an option that can be configured within the change control approach; it is not a mandatory minimum requirement.

AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Chapter 12, Section 12.2, p. 136.

In PRINCE2, a requirement is defined as a need or expectation for a product. To be managed effectively, this need must be documented and agreed upon. This documentation typically occurs in a product description or a dedicated requirements management product. The approval of this documentation ensures there is a clear, shared understanding of what the project must deliver to meet the stakeholders' needs. This forms the basis for defining the project's scope and quality criteria.

B. An event relevant to the project that requires project management consideration: This is the definition of an issue, specifically a request for change, or an off-specification.
C. A prediction about future performance made by studying historical data and past patterns: This describes forecasting, a technique used in planning and control, not a requirement.
D. An uncertain event that, should it occur, will have an effect on the project: This is the definition of a risk.

- AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Appendix C: Glossary, "Requirement," p. 388.

- AXELOS. (2023). Managing Successful Projects with PRINCE2 (7th ed.). TSO (The Stationery Office). Section 8.3.1, "Quality planning," p. 82.