A Project Baseline in PRINCE2 7 represents the approved and agreed-upon reference points against which project performance is measured throughout its lifecycle. It serves as the foundation for monitoring and controlling the project effectively.
The baseline encompasses several critical elements in…A Project Baseline in PRINCE2 7 represents the approved and agreed-upon reference points against which project performance is measured throughout its lifecycle. It serves as the foundation for monitoring and controlling the project effectively.
The baseline encompasses several critical elements including scope, time, cost, quality, benefits, and risk parameters that have been formally approved at the start of a stage or the project itself. These baselines are documented within the Project Initiation Documentation (PID) and Stage Plans, providing a clear benchmark for comparison.
When managing issues within PRINCE2 7, the project baseline becomes essential for assessing the impact of proposed changes or problems. The Issues Practice requires that any deviation from the established baseline be properly evaluated, documented, and escalated through appropriate channels when tolerances are exceeded.
The Project Board sets tolerances around these baselines, allowing the Project Manager operational flexibility within defined limits. Should an issue threaten to push performance beyond these tolerances, an exception report must be raised to the Project Board for decision-making.
Baselines are not static throughout the entire project. They can be formally revised through the change control process when approved changes are incorporated. This ensures that the reference point remains relevant and accurate while maintaining proper governance and traceability of all modifications.
Key baseline documents include the Project Plan, Stage Plans, Work Packages, and the Benefits Management Approach. Each provides specific benchmarks for different aspects of project delivery.
The relationship between issues and baselines is fundamental to PRINCE2 7 governance. Every issue raised must be assessed against current baselines to determine its potential impact on project objectives. This structured approach ensures that decisions are made with full awareness of consequences and that the project remains aligned with its original business justification while adapting to necessary changes through controlled processes.
Project Baseline - Issues Practice Guide
What is a Project Baseline?
A project baseline is a reference point that captures the approved project parameters at a specific point in time. In PRINCE2, the baseline typically includes the approved plans, scope, costs, timelines, and quality expectations that have been formally agreed upon. It serves as the benchmark against which actual progress and performance are measured throughout the project lifecycle.
Why is Project Baseline Important?
The project baseline is crucial for several reasons:
• Performance Measurement: It provides a fixed reference point to compare actual progress against planned progress • Change Control: Any deviations from the baseline can be identified, assessed, and managed through formal change control procedures • Accountability: It establishes clear expectations and commitments that project teams are held accountable for • Decision Making: When issues arise, the baseline helps stakeholders understand the impact of proposed changes • Lessons Learned: Comparing final outcomes against the original baseline provides valuable insights for future projects
How Project Baseline Works in PRINCE2
In PRINCE2, baselines operate at multiple levels:
Project Level: The Project Initiation Documentation (PID) contains the project baseline, including the Project Plan, Business Case, and project controls.
Stage Level: Each Stage Plan becomes a baseline once approved by the Project Board.
Work Package Level: Team Plans may serve as baselines for team-level work.
When an issue arises that may affect the baseline, it must be captured, assessed, and escalated through appropriate channels. The Project Manager assesses issues against tolerances. If the impact exceeds stage tolerances, an Exception Report is raised to the Project Board.
Relationship Between Issues and Baselines
Issues can threaten project baselines in several ways:
• Requests for Change: Formal proposals to modify the baseline scope, cost, or time • Off-Specifications: Products not meeting their specification, potentially requiring baseline adjustments • Problems/Concerns: Situations that may evolve into threats to the baseline
The Issue Register tracks all issues, and the Configuration Management Strategy ensures baseline integrity is maintained.
Exam Tips: Answering Questions on Project Baseline
1. Remember the Purpose: Baseline questions often test whether you understand that baselines exist for comparison and control purposes. The correct answer usually emphasizes measurement and change management.
2. Know the Approval Authority: The Project Board approves the project baseline (PID). Stage Plans are also approved by the Project Board. Understanding who has authority over baselines is frequently tested.
3. Link to Tolerances: Baselines and tolerances work together. Questions may ask what happens when actual performance deviates from the baseline beyond acceptable tolerances.
4. Understand Exception Handling: When baselines cannot be maintained within tolerances, exception procedures apply. Know that Exception Plans replace the current baseline once approved.
5. Configuration Management Connection: Baselines are protected through configuration management. Product baselines ensure the correct versions of products are being used.
6. Watch for Distractor Answers: Incorrect options may suggest that baselines can be casually updated or that the Project Manager alone can modify them. Remember that baseline changes require formal approval.
7. Focus on Control: PRINCE2 emphasizes controlled environments. Answers that maintain control and governance principles regarding baselines are typically correct.
8. Time-Based Questions: If asked when baselines are set, remember they are established during Initiating a Project (for project baseline) and at the end of Managing a Stage Boundary (for stage baselines).