During the closing phase, results are delivered to the customer, books are closed and documentations finalized. However, this is also the time for reflecting on the project. Regardless how the project ended – successful or not – there are always valuable lessons to be learned; mistakes have been made, which should not be repeated by other projects.
The final project report is delivered to the supervisory board. It contains a detailed description of all results obtained, processes used and problems solved. Specifically, it should include:
- The original project assignment
- How the project progressed over time
- All decisions made by the project partners
- All decisions made by the supervisory board
- Quality insurance measures
- Experiences with specific methods, working practices, tools, consulting, rules and standards and cooperation with internal/external partners
- Performance measures and monitoring
During a project, team members typically experience difficult situations, solve problems, cooperate with others in the project, and even make more or less severe mistakes. These experiences should be reflected upon and be collected for later use, such that later projects can benefit from these findings and not repeat the same mistakes over and over again.
Primarily, the project should be reflected upon with respect to matching the customer expectation and generating the expected return on investment. However, there are also much more subtle issues, which offer a great learning experience:
- What went well?
- How did all get along with another?