In the context of PRINCE2 7, the Project Plan is a mandatory management product created during the 'Initiating a Project' process. It serves as a high-level statement detailing how and when a project's objectives—specifically time, cost, scope, and quality targets—will be achieved. It identifies th…In the context of PRINCE2 7, the Project Plan is a mandatory management product created during the 'Initiating a Project' process. It serves as a high-level statement detailing how and when a project's objectives—specifically time, cost, scope, and quality targets—will be achieved. It identifies the major products, activities, and resources required for the entirety of the project lifecycle.
The Project Plan is pivotal for the Business Case, as it provides the planned costs and timescales necessary to verify the project's viability. It acts as the primary baseline against which the Project Board monitors total progress. While it outlines the overall schedule and defines the number and duration of management stages, it remains distinct from and less detailed than the specific Stage Plans used for day-to-day management.
A key aspect of the Project Plan in PRINCE2 7 practice is its dynamic nature. Although baselined at the start to authorize the project, it is updated at the end of each management stage (during the 'Managing a Stage Boundary' process). These updates reflect actual progress from the completed stage and revised forecasts for the remainder of the project. This ensures that the Project Board always possesses a current view of the project's status to make informed decisions regarding continued business justification.
The plan typically includes the schedule, prerequisites, external dependencies, planning assumptions, lessons incorporated, monitoring and control definitions, budgets, and tolerances. It essentially forms the 'contract' between the Project Manager and the Project Board, defining the deliverable expectations and the resources required to achieve them.
Project Plan (Plans Practice) - PRINCE2 Practitioner v7
What is the Project Plan? In PRINCE2, the Project Plan is a mandatory management product that provides a statement of how and when a project's time, cost, scope, and quality targets are to be achieved. It shows the major products, activities, and resources required for the entire project. It acts as the primary baseline against which the Project Board monitors project progress.
Why is it Important? The Project Plan is crucial because it provides the 'how, when, and how much' data necessary to support the Business Case. Without a Project Plan, the Project Board cannot authorize the project, nor can they measure progress against expectations. It ensures that the project remains desirable, viable, and achievable by providing a firm baseline for costs and timescales.
How it Works The Project Plan is created during the Initiating a Project process by the Project Manager. It is not a static document; it is updated at the end of every management stage (during the Managing a Stage Boundary process) to reflect actual progress and any changes to forecasts for the remainder of the project. It provides a high-level overview of the management stages and major milestones, rather than the minute details of daily tasks (which belong in Stage Plans or Team Plans).
Exam Tips: Answering Questions on Project Plan When answering Practitioner questions regarding the Project Plan, keep the following rules in mind:
1. Level of Detail: If a question asks about specific daily activities or detailed product descriptions for a specific week, it is likely referring to a Stage Plan or Team Plan, not the Project Plan. The Project Plan is high-level.
2. The Approval Authority: Remember that the Project Plan must be approved by the Project Board. If a scenario suggests the Project Manager approves it, that is incorrect.
3. The Hard Gates: The Project Plan defines the number and length of management stages. If an exam question involves splitting the project into delivery steps or review points (stage boundaries), you are dealing with the Project Plan structure.
4. Business Case Link: Always look for the connection to the Business Case. If the Project Plan costs exceed the benefits in the Business Case, the project is no longer viable. Questions often test this relationship.
5. Updates: The Project Plan is updated to become a 'Current' Project Plan at the end of each stage. It shows actuals for the finished stage and forecasts for the future stages.