The Capability Maturity Model (CMM) is a widely adopted set of guidelines for evaluating and improving an organization's software development processes. The CMM is a general framework, however, and provides no specific guidance for implementation; instead, each organization must relate CMM characteristics to its own processes. As a consequence, the need has emerged for comprehensive accounts of successful CMM implementations, as well as for detailed descriptions of how software projects are executed in those cases. Such real-world examples can serve as a valuable resource for managers and developers responsible for setting up the CMM and carrying out their own projects. CMM in Practice comprises such a resource. Examining the various stages in the life cycle of a typical software project at Infosys Technologies, the book describes the technical and management processes used to initiate, plan, and execute the project. To enhance the discussion, an actual Infosys project is used as a running example throughout the book. The author, who was one of the main architects behind the quick transition from ISO to CMM at Infosys, shows how these working processes relate to the Key Process Areas of the CMM. He also illustrates how relatively simple and familiar approaches can be combined to raise an organization's software maturity level. CMM in Practice covers these topics and more: *Requirements change management process *Process tailoring *Software metrics and statistical process control *Process database *Process capability baseline *Effort and schedule estimation *Quantitative quality management and defect estimation *Risk management and configuration management *Peer reviews and their quantitative control *Implementing reviews and the NAH syndrome *Data collection and analysis *Quantitative project monitoring and control *Milestone analysis *Audit process *Project closure analysis

Table of Contents:
Preface. 1. Introduction. Process-Based Approach for Project Execution. Capability Maturity Model for Software. Processes at Infosys. Summary. I. PROJECT INITIATION. 2. Proposals and Contracts. Customer and Vendor Interaction. The Proposal. The Contract. Summary. 3. Requirements Specification and Management. Requirements Analysis and Specification. Requirements Change Management. Traceability Management. Example: The WAR System. Summary. II. PROJECT PLANNING. 4. Process Definition and Tailoring. Development Process. Process Tailoring. Summary. 5. Process Database and Process Capability Baseline. Software Metrics and Process Management. Process Database. Process Capability Baseline. Summary. 6. Effort Estimation and Scheduling. Background Information for Estimation. Bottom-Up Estimation. Top-Down Estimation. Scheduling. Summary. 7. Quality Planning and Defect Estimation. Quality Management. Quantitative Quality Management Planning. Summary. 8. Risk Management. Background. Risk Assessment. Risk Control. Examples. Summary. 9. Project Management Plan. Project Management Plan. Example: Project Plan of WAR 2.0. Summary. 10. Configuration Management. Configuration Management Concepts. Configuration Management Process. Document Control. Example: Configuration Management Plan of the WAR Project. Summary. III. PROJECT EXECUTION AND TERMINATION. 11. Life Cycle Execution. High-Level Design. Detailed Design. Build. System Testing. Acceptance and Installation. Summary. 12. Peer Review. Review Process. Data Collection. Monitoring and Control. Introduction of Reviews and the NAH Syndrome. Summary. 13. Project Monitoring and Control. Data Collection. Project Tracking. Quantitative Monitoring and Control. Defect Analysis and Prevention. Summary. 14. Project Audits. Audit Process. Audit Analysis. Summary. 15. Project Closure. Project Closure Analysis. Archiving. Closure Analysis Report for WAR 2.0. Summary. Appendix A. From ISO 9000 to CMM. Appendix B. Managing the Software Process Improvement Project. 0201616262T04062001