Project Closure

Project Closure Analysis

• Is the key to learning from the past so as to provide future improvements.

• To achieve this goal, it must be done carefully in an atmosphere of safety so that
lessons can be captured and used to improve the process and future projects.
Role of closure analysis

• Objective of postmortem analysis is to determine what went wrong, what

worked, what did not, how it could be made better next time.
• This analysis needed to understand the performance of the process on this
project, which in turn is needed to determine the process capability.
• Data obtained during closure analysis are used to populate the process
database(PDB).
• Data from PDB can be used by subsequent projects for planning purposes .
• Also in computing the process capability.
• Closure analysis aims in analyzing and presenting data in proper framework and
at suitable level of abstraction.
• Results should be packaged so that they can be used by others.
Performing closure analysis

• Project manager carries out closure analysis with the help of SEPG quality adviser.
• Person must fill the template properly, using mostly the metrics data .
• Effort data are available from the weekly activity report database.
• Defect data can be gathered from defect control system.
• Size data obtained from projects.
• Planning data available in PMP.
• Data are first analyzed by quality adviser.
• A meeting then held among quality adviser, project leader and others.
• Meeting yields the basis of final closure analysis report.
Closure analysis report

• 1) General and process related information

• Overall productivity achieved and quality delivered, the process used and process
deviations, the estimated and actual start and end dates , tools used etc.
• 2) Risk management
• Risks initially anticipated for the project along with the risk mitigation steps
planned.
• Also lists the top risks.
• 3) size
• Is estimated in terms of simple, medium , complex modules.
• Data on both actual and estimated size are included.
• Productivity of a project is measured in terms of functional points.
• 4) effort
• Report contains total estimated effort and the actual effort in person –hours.
• Estimated effort obtained from PMP.
• Actual effort is the sum of total effort reported in all WAR’s submitted by project
members
• 5) Defects
• Contains summary of the defects found during the project.
• The defects can be analyzed with respect to severity, stage detected, stage injected
• Injection rate and defect distribution is also determined.
• 6) casual analysis
• It involves looking at large variations and then identifying their causes, generally
through discussion and brain storming.
• 7) Process assets.