Task Descriptor: Close-out Project
Prepare a final assessment for project acceptance which, if successful, marks the point when the customer accepts ownership of the software product. Complete the close-out of the project by disposing of the remaining assets and reassigning the remaining staff.
Based on Method Task:  Close-out Project
Relationships
RolesMain: Additional: Assisting:
InputsMandatory: Optional:
  • None
External:
  • None
Outputs
Steps
Conduct project acceptance review

When the end of the project is near, the project manager organizes a meeting with the project team and the stakeholders to confirm that the project fulfilled the project goals.

If some of the project goals have not been satisfied, stakeholders could decide to accept the product conditionally upon certain corrective actions being taken. In this situation, the project manager would need to plan how to resolve the remaining issues. If the goals that were not fulfilled are critical for the stakeholders, they could decide to postpone the project acceptance until the issues are resolved.

Conduct a project retrospective review
A post-completion review is conducted by the project manager. The review involves all members of the project team. The objective of this review is to established what lessons were learned. These lessons can be recorded and used on future projects.
Close-out the project

When the project is accepted there are often some remaining administrative tasks such as: 

  • Archiving the project assets.
  • Transferring any remaining non-deliverable hardware and environment assets to the owning organization's pool of assets.
  • Transferring project measurements and lessons learned to the corporate repository. 
Properties
Multiple Occurrences
Event-Driven
Ongoing
Optional
Planned
Repeatable