SUMMARY

12.3 SUMMARY

A project does not end with the delivery and installation of the software; before it is closed, it must be used for learning. Project closure analysis is one method to achieve this goal.

Following are some of the key takeaways from the Infosys approach to project closure:

         Keep the project closure analysis metrics-based. Analyze the data to understand the performance of the project and the causes for any major deviations. These causes can serve as a source of improvement initiatives.

         The metrics analysis should report the final quality delivered, the productivity achieved, the distribution of effort, the distribution of defects, the defect removal efficiency of various quality activities, and the cost of quality.

         Collect reusable process assets such as plans, checklists, standards, and guidelines, and make them available for others.

With respect to the CMM, project closure is not a direct requirement of the KPAs dealing with project management. However, the closure report provides the data for the process database and process capability baseline, which are necessary to satisfy many of the requirements of the Project Planning KPA and the Integrated Software Management KPA. They also aid in learning and recordkeeping, which are required at level 3.