Project Closure

When a project is finished, and all deliverables are released to production, the product will be in hands of Managed Services to monitor, maintain, and update. The project goals, budget and project issues are evaluated. Project success will be celebrated and Kabisa will promote the project success internally and via social media.

Why

The Project Closure serves as the official closure of the project, on three levels:

  1. Towards the customer, on a contractual and financial level
  2. Towards Managed Services: 100% transfer of the product
  3. For other Kabisa processes: marketing & résumé updates

Prepare for success

  • Deliver a proper Project Status Report at the end of every sprint. This will make sure there are no surprises at the closure of the project.
  • Have Managed Services involved during the project, so there is no “big bang” knowledge transfer at the end.

How

Compose a Project Closure Report (PCR) directly after:

  • the last sprint of the project has finished, and
  • the final knowledge transfer to managed Service has been done, and
  • the last release by the project team has been done

Include all hours & budget information in the PCR, with clear links to the invoices. Explain and discuss the details of the PCR with the customer. Execute the transfer to Managed Services similar to the transfer for earlier releases during the project. Bring the Kabisa marketing team in contact with the customer for a reference case. Have all team members ask for customer feedback and update their résumé.

Definition of Done[1]

  • PCR sent to customer (Product Owner[2] and sponsor) and Kabisa (account manager and operational manager). Content of the PCR discussed with the customer.
  • Managed Services is confident to give support on the final product.
  • Reference case has been written and approved by the customer.
  • Team member have received customer feedback and updated their résumés.

Real Life Example

Interview met Fatboy

Notes

  1. Definition of Done - A shared understanding of expectations that the Increment must live up to in order to be releasable into production. Managed by the Development Team.
  2. Product Owner - The Product Owner plays a crucial role in the development of a great software product. He or she is responsilble for maintaining the Product Backlog.