|CM 4.7: Recording Project History|
|From||Product||to||Methods||Tool Req.||Ext. Norms|
/ISO IEC 12207/
Probl. Resol. Proc.:
|being proc.||Existing||Project Plan||-||-|
Progress Report ,
Final Project Report ,
Case Report ,
Internal Message ,
|-||-||All||Project History||PM7 ,
|being proc. /
+ "Chapter" are extra columns from the original printed version of GD 250Project History.
The Project History is the "project log" intended to document the course of the development. It maintains information about the project development, in particular information about difficulties and problems as well as the measures chosen to eliminate them and offer solutions.
The Project History also has to maintain statistical information about the realized activities, deviations from and modifications to the plan, requested, realized and rejected changes, frequency of errors, error types and vulnerability of errors. The required information is obtained from the Project Plan and Project Manual by comparing Internal Messages generated during the control activities, and from the Report Documents written by SD, PM, QA and CM.Project History is a documentation of the course of the development, the decisions, problems and difficulties as well as of the corresponding solutions. It is used to improve the sequence and the calculation for future projects ("lessons learned").
Deviations from the Plan
|EVT - Earned Value Method||Generate|
|Product||Functional Tools Requirements|
|Project History.Planning Statistics||SPM06 - Supporting Project Control and Steering|
|/ISO IEC 12207/||Problem Resolution Process||Problem Resolution||(s. Part 3 - ISO 3.2.2)|
|Management Process||Execution and Control||(s. Part 3 - ISO 3.2.3)|
|Improvement Process||Process Improvement||(s. Part 3 - ISO 3.2.3)|
|GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster|