In the context of PRINCE2 7 and the Issues Practice, Baseline Management is a critical control mechanism that establishes fixed reference points for project products, plans, and documentation. A baseline represents the state of a 'Configuration Item' (a product or set of products) at a specific poi…In the context of PRINCE2 7 and the Issues Practice, Baseline Management is a critical control mechanism that establishes fixed reference points for project products, plans, and documentation. A baseline represents the state of a 'Configuration Item' (a product or set of products) at a specific point in time that has been reviewed and agreed upon. Once a product is baselined, it is effectively 'frozen' and can only be changed through a formal change control procedure.
Within the Issues Practice, baselines serve as the standard against which potential changes and deviations are measured. An issue—defined as any event relevant to the management of the project which requires attention—often arises as a challenge to a baseline. For instance, a 'Request for Change' asks to alter a baselined product, while an 'Off-Specification' indicates that a product fails to meet the criteria defined in its baselined description. Without these fixed reference points, it would be impossible for the Project Manager or Project Board to assess the impact of an issue on time, cost, scope, or quality.
Baseline management prevents 'scope creep' and ensures version control. For example, when the Project Initiation Documentation (PID) is approved, it becomes the baseline for the project's scope. Any subsequent deviation requires an impact analysis to determine if the change is viable. This aligns with the principle of 'Manage by Exception,' as tolerances are set against these baselines. By strictly managing these reference points, PRINCE2 ensures that all stakeholders share a single version of the truth regarding what has been created and what is currently agreed upon, thereby maintaining the integrity and stability of the project environment.
Mastering Baseline Management in PRINCE2 Practitioner v7
What is Baseline Management? Baseline management is a critical component of the Issues practice (formerly part of the Change theme). A baseline is a snapshot or a reference level against which an entity is monitored and controlled. In PRINCE2, as soon as a product—whether it is a management product (like the Project Initiation Documentation) or a specialist product (like a software module)—is approved, it becomes 'baselined'. This means the version is frozen and preserved.
Why is it Important? Without baseline management, projects act on moving targets, leading to uncontrolled change (scope creep). It is vital because: 1. It provides a fixed reference point to compare actual progress against planned expectations. 2. It ensures version control, so everyone works on the correct document or software build. 3. It provides an audit trail showing who changed what, when, and why. 4. It allows for the safe storage and retrieval of project assets.
How it Works Baseline management is executed through Configuration Management. The process involves: 1. Identification: Every product is given a unique identifier and version number (e.g., v1.0 upon approval). 2. Control: Once baselined, a product cannot be modified arbitrarily. To change a baseline, a formal Request for Change (a type of Issue) must be raised. Only once the change is approved by the relevant authority (Change Authority or Project Board) can a new version (e.g., v1.1) be created and baselined. 3. Status Accounting: This involves creating reports (Product Status Accounts) that detail the current state of products (e.g., 'Draft', 'Baselined', 'Archived'). 4. Verification: Audits are performed to ensure the recorded status matches the actual physical products.
Exam Tips: Answering Questions on Baseline Management In the Practitioner exam, you will need to apply this logic to the provided scenario. Keep these specific strategies in mind:
1. Check the 'Approval' Status: Read the scenario carefully. Has the document or product been signed off or approved? If yes, it is a baseline. Any answer option suggesting the Project Manager can simply 'edit' or 'update' it without raising an issue is incorrect.
2. Link to Issues Practice: If a question asks how to handle a flaw found in a finished product, recognize that because the product is finished (baselined), this is an Issue (specifically a Request for Change or Off-Specification). You must follow the issue and change control procedure.
3. Identify the Correct Management Product: - If the question asks for the history of a specific product, look for Configuration Item Records (CIRs). - If the question asks for a report on the status of a group of products (e.g., 'what did we finish last week?'), look for the Product Status Account.
4. Preservation vs. Change: Baseline management is about preservation. If a question is about protecting assets from unauthorized access or damage, it relates to the Configuration Management strategy within the Issues practice.