Decide on closure phase release

The decision on closure phase release concludes the provision of goods or services within the scope of the solution development and creates the prerequisite for the work in the closure phase.

The outcomes of the entire solution development are checked and accepted or rejected. The phase is completed, and the closure phase as well as the resources required for it are released.

At the end of the deployment or execution phase, the phase report and - in the execution phase - the last release report are approved. The project sponsor decides on the end of solution development and on release of the closure phase.

If the solution development was agile, the development team is dissolved.

A decision is made

• whether the phase is concluded or whether there are additional outcomes to be developed prior to conclusion of the phase, or
• whether the closure phase is released.

• Acceptance milestone
• Phase report
• Release report
• Project management plan
• Project status report

• Add further release criteria to closure phase release checklist.
• Coordinate the decision in the core organization.
• Make formal decision on closure phase release or reject outcomes.
• If the decision is positive:
  • Release resources for the next project phase.
  • Inform those affected about the decision.

• Closure phase release checklist
• Closure phase release milestone
• List of steering project decisions
• QA and risk report