Context of the Project Close-Out Document

• Project is coming to an end, but hasn’t ended yet.

Project Close-Out Document Audience

• Primary audience– Sponsors (Linda and Scott)– Customers (ISEEK/Nate, Roxie, Tia)– Team (Developers/Tim and Jack, Designer/Royce, QA/Yan,

Testers/Natalie and Elena, BA/Cynthia, Usability/Nicole)• Secondary audience

– Other depts w/in organization– Your supervisor– Natalie and Elena

• Other audiences to take into account:– Consider dept leaders vs. dept members– What about Todd and Joe: where do they fit?– Do all of the team members need to be members of the primary

audience?– Do other depts w/in your org need to be secondary audience members?

If so, which depts?

Project Close-Out Document Purpose

(i.e., what do you hope to accomplish with this document?)• To articulate a sense of accomplishment

• To learn from mistakes made on the project/Prepare for the next project

• Record the project and its final phase• Find out far we are from the finish line, i.e. come to

agreement on exit criteria• Summarize the project, if its objectives were met, and if it

has been built to specification (reqs, specs, change requests)

• To bring the project to a close• Summarize deliverables (e.g., business reqs, test plans)• Transition the project from development to maintenance

(project to product)

Important Information to Include in the Close-Out Document

• Successes• Lessons learned• Name who the responsible parties are upon

transition• Name project team members• Plan for maintenance• Go live dates• Known bugs and plans to address them• Change requests that were submitted but not

built/future features• Exit criteria