In the context of the PRINCE2 7 Starting Up a Project process, the activity 'Capture Previous Lessons' is a critical early step that operationalizes the core principle 'Learn from Experience.' Its purpose is to ensure that the new project does not reinvent the wheel or repeat the mistakes of the pa…In the context of the PRINCE2 7 Starting Up a Project process, the activity 'Capture Previous Lessons' is a critical early step that operationalizes the core principle 'Learn from Experience.' Its purpose is to ensure that the new project does not reinvent the wheel or repeat the mistakes of the past before any detailed planning or significant resource commitment takes place.
The Project Manager facilitates this activity, often involving the Executive and those with knowledge of previous similar initiatives. The process involves reviewing Lessons Reports from completed projects, consulting corporate or programme management, and analyzing external industry standards. The objective is to identify historical anomalies, successful techniques, and specific risks that are relevant to the current mandate.
The immediate output of this activity is the creation of the Lessons Log. Although this log is a dynamic document maintained throughout the project lifecycle, it is populated at this stage with these initial findings. For instance, if a past project failed due to ambiguous acceptance criteria, the Lessons Log would record a requirement for stricter definitions in the current project's Product Description.
These captured lessons act as vital inputs for the Project Brief and the Initiation Stage Plan. By integrating this knowledge immediately, the project management team can refine their approach, adjust estimates, and implement safeguards against known pitfalls. Ultimately, capturing previous lessons ensures the project begins with a realistic perspective, leveraging organizational wisdom to increase the likelihood of delivering value.
Introduction In PRINCE2 7th Edition, Capture Previous Lessons is a specific activity performed within the Starting Up a Project process. It serves as the initial, practical application of the core principle Learn from Experience. Before any detailed planning takes place, the project management team must validate that they are not about to repeat historical mistakes or reinvent existing solutions.
Why is it Important? Organizations often run projects that are similar to previous undertakings. Failing to capture lessons leads to: 1. Inefficiency: Wasting time creating approaches that already exist in the corporate knowledge base. 2. Recurring Errors: Falling into the same pitfalls regarding risk, quality, or vendor management that plagued previous projects. 3. Poor Estimation: creating an unrealistic Business Case by ignoring historical data on costs and timescales.
What is it? It is an investigatory activity led by the Project Manager. It involves gathering relevant experience from inside (and sometimes outside) the organization to inform the current Project Brief and Project Approach.
How it Works The process flows as follows: 1. Input: The Project Manager takes the Project Mandate and reviews the organization's knowledge base (previous End Project Reports, Lessons Reports, and corporate standards). 2. Analysis: The PM filters this data to find lessons relevant to the current project's scope, technology, or context. 3. Documentation: These insights are recorded in the Lessons Log. Note: This is when the Lessons Log is first created. 4. Application: The lessons define how the project is set up (e.g., choosing a specific agile approach because it worked previously) and help refine the draft Business Case.
Exam Tips: Answering Questions on Capture Previous Lessons For the Practitioner exam, questions will often present a scenario. Apply these strategies:
1. Distinguish the Artifacts If the question asks what is created during this activity, the answer is the Lessons Log. Do not confuse this with the Lessons Report (which is an output at the end of a stage or project). The Log acts as a repository for lessons to be applied now.
2. The Timing Key If the scenario describes the very beginning of the project (pre-initiation), the context is Starting Up a Project. If the Project Manager is looking at history to justify the project, they are capturing previous lessons.
3. The 'Who' The Project Manager is responsible for this. While they may consult the Executive or Senior User, the PM does the work. If an exam option suggests the 'Project Board' creates the Lessons Log, it is likely incorrect.
4. Scenario Relevance Read the scenario carefully. If the text says, 'The organization has a history of poor communication with stakeholders,' the correct answer to a 'Capture Previous Lessons' question might involve setting up a specific Communication Management Approach based on that failure.
5. Justification Always link this activity back to the business justification. If a question asks why we capture lessons during startup, the strongest answer usually relates to ensuring the Business Case is realistic and achievable based on evidence.