PRINCE2® PROCESSES – Initiating a Project (IP)

See our training for PRINCE2.

The purpose of the Initiating a Project process is to establish solid foundations for the project, enabling the organisation to understand the work that needs to be done to deliver the project’s products before committing to a significant spend.

The objective of the Initiating a Project process is to ensure that there is a common understanding of:

• The reasons for doing the project, the benefits expected and the associated risks
• The scope of what is to be done and the products to be delivered
• How and when the project’s products will be delivered and at what cost
• Who is to be involved in the project decision making
• How the quality required will be achieved
• How baselines will be established and controlled
• How risks, issues and changes will be identified, assessed and controlled
• How progress will be monitored and controlled
• Who needs information, in what format, and at what time

Other products created and ready for use when the project commences are:

• Risk Management Strategy and Risk Register
• Configuration Management Strategy, Initial Configuration Item Records and Issue Register
• Quality Management Strategy and Quality Register
• Communication Management Strategy
• Project Controls
• Role Descriptions
• Project Management Team Structure
• Project Plan
• Product Descriptions
• Benefits Review Plan
• Detailed Business Case
• Project Initiation Documentation

If you've attended our PRINCE2® Foundation or PRINCE2 Practitioner course and want to start a project using PRINCE2 back at work, you'll need somewhere to start.

Here you can download official PRINCE2 project templates to help you to manage your project effectively.

You can download a zipped folder containing all of the PRINCE2 project templates or select individual templates from the list below:

PRINCE2 Project Templates:

• Benefits Review Plan
• Business Case
• Checkpoint Report
• Communication Management Strategy
• Configuration Item Record
• Configuration Management Strategy
• Daily Log
• End Project Report
• End Stage Report
• Exception Report
• Highlight Report
• Issue Register
• Issue Report
• Lessons Log
• Lessons Report
• Project Plan
• Product Description
• Product Status Account
• Project Brief
• Project Initiation Documentation
• Project Product Description
• Quality Management Strategy
• Quality Register
• Risk Management Strategy
• Risk Register
• Work Package

PRINCE2® PROCESSES – Closing a Project (CP)

See our courses for PRINCE2.

The purpose of the Closing a Project process is to provide a fixed point at which acceptance for the project product is confirmed and to recognize that objectives set out in the original Project Initiation Documentation have been achieved (or approved changes to the objectives have been achieved), or that the project has nothing more to contribute.

The objective of the Closing a Project process is to:

• Verify user acceptance of the project’s products
• Ensure that the host site is able to support the products when the project is disbanded
• Review the performance of the project against its baselines
• Assess any benefits that have already been realized, update the forecast of the remaining benefits, and plan for a review of those unrealized benefits
• Ensure that provision has been made to address all open issues and risks, with follow-on action recommendations.

The main products of this process are as follows:

• Project Plan updated with final actual
• Product Status Account covering the status of all products for the project
• Issue register to identify any outstanding issues
• Follow-on action recommendations created with any outstanding issues to be addressed
• Configuration item records updated with current status of products
• Benefits review plan updated with dates for benefits realization
• Acceptance records for products completed
• End project report created
• Lessons Report created
• Close Issue, Risk, Quality registers, Daily and Lessons Log