Closing a Project Process

The correct answer is that all project team members have been formally released from their project assignments and access to project systems has been revoked.

In PRINCE2 7, the Prepare Planned Closure activity is part of the Closing a Project process. A critical aspect of proper project closure is ensuring that resources are formally released back to their respective line managers or resource pools. This includes:

• Formal release of team members from project assignments
• Revocation of access to project systems and resources
• Confirmation that resources are no longer allocated to the project

This formal release is essential because:
1. It ensures resources can be reallocated to other work
2. It provides clear accountability and prevents unauthorized access
3. It marks the definitive end of team members' project responsibilities
4. It is a prerequisite for confirming the project can be closed

Why the other answers are incorrect:

The option about timesheets and expense claims, while administratively important, is a financial management activity that should be handled through normal business-as-usual processes and is not a specific PRINCE2 closure requirement.

The option regarding performance evaluations is a human resources management activity that may occur independently of project closure and is not a prerequisite defined in PRINCE2 for completing the Prepare Planned Closure activity.

The option about documenting work in the lessons log is part of lessons management, which feeds into the End Project Report, but the specific requirement about knowledge transfer sessions is not a mandatory confirmation point for completing Prepare Planned Closure in PRINCE2 7.

The objective of the closing a project process regarding acceptance of the project product is to verify that the customer has accepted the project product and that operational and support arrangements are in place.

This is correct because the closing a project process in PRINCE2 7 has specific objectives around formal acceptance and transition. The process ensures that:
- The customer has formally accepted the project product (not just reviewed, approved, or acknowledged it)
- Operational and support arrangements are confirmed to be in place, ensuring the product can be maintained and supported after project closure

This combination of acceptance and operational readiness is essential for proper project closure.

Why the other answers are incorrect:

The second option mentions 'approved' rather than 'accepted' and focuses on quality activities being completed according to the Product Description. While quality activities are important throughout the project, the closing process specifically focuses on acceptance and operational readiness, not on verifying quality activity completion.

The third option uses 'acknowledged' which is weaker than 'accepted' and incorrectly links acceptance to performance metrics being documented in the lessons report. The lessons report is about capturing learning, not about confirming product acceptance and operational arrangements.

The fourth option uses 'reviewed' instead of 'accepted' and incorrectly suggests handover documentation goes to the change authority. The change authority deals with changes during the project, not with final handover and operational arrangements at project closure.

The correct answer is End of Project Report.

The End of Project Report is the management product that provides formal confirmation that the project has delivered what was required and contains the recommendation for project closure. This report is created during the Closing a Project process and serves as the definitive document that:

• Confirms whether the project's objectives have been achieved
• Summarizes the project's performance against the original Project Initiation Documentation
• Documents lessons learned throughout the project
• Provides a formal recommendation to the Project Board on whether the project should be closed
• Reviews how the project performed against time, cost, quality, scope, benefits, and risk targets

Why the other answers are incorrect:

The End Stage Report is produced at the end of each management stage (not just at project closure) and provides an assessment of that specific stage's performance. It does not provide formal confirmation of overall project delivery or recommend project closure.

The Project Initiation Documentation is created at the start of the project and defines what the project is aiming to achieve. It serves as the baseline against which performance is measured, but it does not confirm delivery or recommend closure.

The Benefits Review Plan outlines how and when benefits will be measured after project closure. While it's important for post-project evaluation, it does not provide confirmation of project delivery or recommend closure.