9.3 Closeout Actions

 < Day Day Up > 



Before closing out the project, some housecleaning activities need to be accomplished. In order to properly end the program and terminate the activities supporting the product, you should complete these actions:

  1. Produce a written Software Project History containing both objective and subjective information about the project.

  2. Distribute the project history to all project members.

  3. Place Project History conclusions into the project binder for review when working on the next project.

  4. Conduct a postmortem meeting and report all results and findings.

  5. Complete all closeout paperwork.

When you write the Software Project History document, a good place to start is with the compiling all of the project status meeting notes and minutes into a chronological record of events. Remember to document concerns, decisions, and contentious items that occurred in the meeting. It is always good to reflect back on areas that caused strong feelings and try to evaluate why those feelings were expressed. You should gather all of the reports, written opinions, and so on and try to create a thorough history that reflects what you and the Core Team know to be the events that have occurred.



 < Day Day Up > 



Managing Software Deliverables. A Software Development Management Methodology
Managing Software Deliverables: A Software Development Management Methodology
ISBN: 155558313X
EAN: 2147483647
Year: 2003
Pages: 226

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net