Starting Up a Project Process

The correct answer is Project Initiation Documentation.

In PRINCE2 7, the primary purpose of the Initiation Stage is to establish a solid foundation for the project by creating the Project Initiation Documentation (PID). This is the key deliverable that must be produced and approved before the project can proceed to the subsequent delivery stages.

The PID is a comprehensive document that defines the project in detail, including:
- Business Case justification
- Project objectives and scope
- Project approach and delivery strategy
- Roles and responsibilities
- Quality management approach
- Risk management approach
- Communication management approach
- Initial project plan and stage plans

The Project Board uses the PID to decide whether to authorize the project to move forward into the delivery stages. This authorization happens at the end of the Initiation Stage during the 'Authorize the Project' activity.

Why the other answers are incorrect:

The option mentioning 'Stage Plan for all remaining stages' is incorrect because PRINCE2 follows a principle of management by stages. While the PID includes an overall Project Plan, detailed Stage Plans are only created for the next stage (not all remaining stages), as this would violate the principle of managing by exception and planning appropriately.

The option about 'Initiation Stage Plan' is incorrect because the Initiation Stage Plan is created during the Starting up a Project process, before the Initiation Stage begins. It's not the primary deliverable of the Initiation Stage itself. Risk and Issue Registers are components within or referenced by the PID, not separate primary deliverables.

The option mentioning 'detailed delivery stage resource schedules' is incorrect because PRINCE2 advocates proportionate planning. Detailed resource schedules for all delivery stages would be excessive and inflexible at this point. The PID contains high-level plans with detailed planning done stage-by-stage.

The correct answer is: 'The selected delivery method and key considerations for producing the project's products'.

In PRINCE2 7, the project approach is a fundamental concept established during project initiation. It specifically refers to the chosen delivery method and the key considerations needed to create the project's products. The project approach addresses how the project will be delivered - whether through traditional methods, agile approaches, or a hybrid combination - and considers critical factors such as:

• The solution approach (build, buy, or customize)
• Key delivery considerations and constraints
• The overall strategy for product creation
• Any specific delivery requirements or limitations

The project approach is documented in the Project Brief during the Starting up a Project process and further refined in the Project Initiation Documentation (PID).

Why the other answers are incorrect:

The option about strategic alignment and organizational vision statement is too broad and focuses on high-level strategic considerations rather than the practical delivery method and product creation approach that defines the project approach.

The option emphasizing comprehensive risk management strategy and mitigation plans describes risk management activities, which while important to projects, are not what the term 'project approach' specifically refers to in PRINCE2 7. Risk management is addressed separately in the Risk theme.

The option that includes detailed technical specifications and resource allocation plans goes beyond the scope of the project approach. While the approach considers delivery methods, it doesn't typically include the level of detail suggested by 'detailed technical specifications and resource allocation plans' - these would be developed later in project planning activities.

The correct answer is 'The lessons log'.

In PRINCE2 7, the lessons log is specifically designed to record experiences, insights, and lessons learned throughout the project lifecycle. It serves as a living document that captures valuable information as it occurs during the project, making these lessons available for continuous improvement both within the current project and for future projects.

The lessons log is maintained throughout the project and is used to:
- Capture lessons as they arise during the project
- Record what worked well and what didn't
- Document insights that could benefit the current or future projects
- Facilitate organizational learning

Why the other answers are incorrect:

The issue register is used to capture and manage issues (problems or concerns) that occur during the project and require management action. It is not designed for recording lessons learned.

The lessons report prepared at project closure is a summary document created at the end of the project that consolidates the lessons from the lessons log. While it does contain lessons learned, it is not the document used to record lessons during the project - it's a final report based on the lessons log.

The daily log is an informal document used by the Project Manager to record informal issues, required actions, and other information that doesn't warrant formal recording elsewhere. While it may contain useful notes, it is not the designated document for capturing lessons learned for future projects.