- Pass The PRINCE2 Exam First Time
- PRINCE2 In Bite-Sized Chunks.
- Key Foundation and Practitioner Learning Points - PRINCE2
- Change Management
- Managing and Controlling a PRINCE2 Delivery Stage
- PRINCE2 Project Closure
- PRINCE2 Starting Up A Project Process
- Using PRINCE2 Initiating A Project Process
- PRINCE2 Authorizing Initiation
- The PRINCE2 Controlling a Stage Process
- Appoint The Executive and Project Manager
- Authorising a PRINCE2 Project
- Authorize a Stage or Exception Plan
- Authorize a Work Package
- Capture and Examine Issues and Risks
- Change Control
- Change control procedures
- Configuration Management
- Configuration Management and Change Control
- Controlling a stage
- Create the PRINCE2 Communication Management Strategy
- Creating a PRINCE2 Plan
- Design and appoint the Project Management Team
- Execute a PRINCE2 Work Package
- Give Ad-hoc direction in a PRINCE2 project
- Hand over products and evaluate a PRINCE2 project
- Managing A Stage Boundary
- Managing Product Delivery process
- PRINCE2 - Authorise Project Closure
- PRINCE2 - Directing a Project PRocess
- PRINCE2 Configuration Management and Change Control
- PRINCE2 Controls and Tolerance
- PRINCE2 Estimating Techniques
- PRINCE2 Management Stages
- PRINCE2 Plans
- PRINCE2 Principles
- PRINCE2 Product-based Planning video
- PRINCE2 Product-based planning technique
- PRINCE2 Progress reporting
- PRINCE2 Quality Theme
- Plan The Next Stage or Exception Plan
- Plan the Initiation Stage in PRINCE2
- Prepare the PRINCE2 Quality Management Strategy
- Prepare the Risk Management Strategy
- Prepare the outline Business Case
- Product Based Planning
- Project Board and Project Manager PRINCE2 Controls
- Project Startup
- Quality Expectations and Acceptance Criteria
- Quality Management Strategy
- Quality review technique
- Report Highlights
- Reporting PRINCE2 Stage End
- Select the project approach and assemble the Project Brief
- Set up the PRINCE2 project controls
- Simple Study Aid
- Tailoring PRINCE2 Themes
- Take corrective action
- The Closing a Project Process
- The Controlling a Stage Process
- The Core Seven
- The Only PRINCE2 Sample Practitioner Exam Paper On The Internet!
- The PRINCE2 Business Case
- The PRINCE2 Change Theme
- The PRINCE2 Initiating a project process
- The PRINCE2 Process Sequence
- The PRINCE2 Processes
- The PRINCE2 Quality Review Technique
- The PRINCE2 Risk Management procedure
- The PRINCE2 Themes
- The Prince2 Process Sequence
- The risk management procedure
- prepare for planned or premature closure
- The PRINCE2 Article Library
- 38 Speedy Power Keys For Your PRINCE2 Project Health Check.
- Carrying out a PRINCE2 Quality Check
- The Product Description
- The plans theme and product based planning
- Creating a PRINCE2 Product Description
- PRINCE2 - Keeping Your Project On track - Part 2
- PRINCE2 Article Database
- PRINCE2 – Keeping Your Project On Track – PART 1
- The PRINCE2 Risk Theme – Uncertainty Mastered!
- The PRINCE2 Work Package
- The Secrets Of tailoring PRINCE2
- The Use and Content of the Issue Register and Issue Report
- PRINCE2 Foundation and Practitioner Exam Tips
- Agile verses PRINCE2 - a new species in evolution
- PART TWO of my Configuration Management In PRINCE2 Video
- PRINCE2 Quality
- Real-World PRINCE2 Planning
- Reviewing the progress on a PRINCE2 project
- Risk management
- Things You Might Not Know About PRINCE2
- The PRINCE2 Project Board and Governance
Hand over products and evaluate a PRINCE2 project
Hand over products and evaluate the project.
Once the project is completed its products then these must be passed on to those who will operate and maintain the products within their operational life. It is important that this happens before the project actually closes.
This may happen as a single release at the end of the project, or the project may have been undertaking phased delivery and hence hand products over to the customer during the stages, in which case this would be the final product or products of the phased delivery.As part of handing over these products, the benefits review plan may need to be updated to include the resources and timing for post-project benefit reviews tied to the performance of the project products in their operational use.
It is important to understand that it is not a responsibility of the project to carry out such post project benefit reviews, only to plan for them.
The project manager working with the project management team will prepare follow-on action recommendations to include any uncompleted or unfinished work. These will include any current issues and any outstanding risks which if they were to occur, would do so in the operational life of the end product.
The project manager will want to agree who is the owner and manage these issues and risks after the project has closed.
The Configuration Management Strategy document should be checked to confirm how the products are to be handed over to those who will look after them in their operational life.
This may include ensuring that suitable service agreements or maintenance contracts have been drawn up and in place (it is not normally the responsibility of the project to fund such agreements and contracts).
The operations and maintenance groups need to confirm that they have accepted the products and the project manager should obtain appropriate acceptance records and add to the project files.
This will then transfer responsibility for the products to those parts of the organisation. Don’t forget to update each product’s Configuration Item Record to reflect that their status is now ‘operational’.
It is important for organisation to learn from their experiences with projects, in particular by capturing what actually happened, then be used to improve estimates for future projects. One of the seven principles within PRINCE2 is to learn from experience, and the following actions will help us do that:
Refer to the original Project Initiation Documentation baselines in the initiation stage and against this review he approved changes as defined by its latest version. Using input from the project management team, the project manager will prepare an End Project Report.
This should include an assessment of the results of the project against the expected benefits in the Business Case, how the project performed against its objectives, having seen performed, and a review of the project products.

In a similar way the project manager will prepare a Lessons Report that may be applied for future projects. This will be sent to corporate or programme management, and it would be a good idea if a copy was sent to your organisation’s project office so that these lessons can be embedded within the organisation.
The Lessons Report should document what went well, what went badly, and any recommendations for the future. The review should be held of any useful measurements such as work effort costs and duration, how quality checking tracked errors or not, and any useful ideas about how to tailor PRINCE2 for similar projects in the future.
When the project manager has confirmed that the project can be closed, he or she will send a closure recommendation to the project board. Here are the actions project manager should ensure now happens:
- Use the communication management strategy to identify which stakeholders or interested parties need to know that the project is closing
- Close down all of the registers and logs.
Secure and archive all project information using the Configuration Management Strategy to determine how it should happen, prepare and send a draft project closure notification for review tby the project board stating that the project has now closed.
For more information CLICK HERE



