Closure and Lessons Learned
Level 4 Β· The life of a project
How a project is closed properly, and what is learned from it. Why the gains it promised are checked later, often after the team has gone.
Course contentsLesson 9 of 11
Level 1 Β· What a project is
Level 2 Β· Who runs a project
Level 3 Β· Starting a project
Level 4 Β· The life of a project
Level 5 Β· Ways to run a project
After this lesson you can
- List the steps of closing a project
- Write a lesson the next team can use
- Tell a result apart from a benefit
11 mincovers 3 glossary entries
Worth reading first: Project Life Cycle and Phases
How to close a project, and check it was worth it
Project closure is the last phase of a project. The team hands over the result and gets a written sign-off that it was accepted. Then contracts are closed, the last bills are paid, files are stored and people move to new work. Skipping these steps can leave bills open for months.
The sign-off is the step people forget. Without it, the client can keep asking for one more change, and the project never quite ends. A short signed note that says the result was accepted draws the line.
Lessons learned are what the team found out along the way. They cover what went well, what went badly and what to do next time. Good teams write them down all through the project, not only in a meeting at the end, when half the detail is gone.
A useful lesson says what to do, not just what happened. Suppliers were slow teaches nothing. Book the German supplier six weeks ahead, not two, is something the next team can act on. Keep the lessons where the next project will find them.
Benefits realization is checking that the project gave the value it promised. A project makes a result, such as a new website. The benefit is what that result does, such as more sales. The two are not the same thing.
Benefits often show up long after the close. A new system may take a year to save the money the business case promised. So someone, often the sponsor, must own each benefit. They track it and report on it after the team has gone.
The common mistake is stopping when the work is done and skipping the close. Another is counting the result as the benefit. A new app is the result. Fewer calls to the help desk is the benefit.
Worked example
Emma checks the gains in December
Emma's new shop website goes live in May. She gets the client's sign-off, pays the last bill and frees her 2 designers.
The business case promised 15% more online sales within a year. In December the sponsor checks the numbers. Sales are up 12%, and the report says what is still missing.
The words for this lesson3
Check yourself
Is a project's result the same as its benefit?
Finished this lesson?
Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.