A project closeout report is like a status report on steroids. It summarizes project results, risks and issues encountered, and lessons learned. It also presents final performance numbers, including schedule and budget performance, and earned value. This section describes what usually goes in a project closeout report, and identifies Project reports you can run to obtain the information you need.
Figure 18-1. The most important part is the John Hancock from whoever has authority to accept the project. You can add other elements like a list of completed deliverables if you want to be very clear about what the customer is accepting.
Audiences want to know what's important, but they don't want to spend time digging. A project closeout report summarizes results for quick and easy reading, as the example in Figure 18-2 illustrates. (Let folks with a penchant for detail and too much time on their hands search the entire project archive, if they want.)
In addition to the performance reports described in the next section, the closeout report includes an analysis of what happened, and a synopsis of the most significant results. Here are the main items in a project closeout summary:
Overview. This section is like the Letter to Shareholders that a CEO writes for a company's annual report; it's a 50,000-foot view of what the project accomplished. ...