An analysis of two case studies to understand the process improvement<br />Presented by<br />Priyaashree<br />Rakesh<br />Vishaal<br />Indranil<br />Rohit Prasad<br />Surya<br />CMMI <br />
Introduction<br />The CMMI is a framework for business process improvement<br />It is NOT an engineering development standard or a development life cycle<br />There are currently three "flavours" of CMMI called constellations. <br />-CMMI for Development - 22 Process Areas.<br />-CMMI for Acquisition - 21 Process Areas.<br />-CMMI for Services - 24 Process Areas.<br />The three constellations share 16 "core" process areas.<br />Process Areas are organized in two main ways, called "Representations“.<br />Staged<br />Continuous <br />Maturity Level and Capability Level<br />
Brief History of CMMI<br />In the 1980s a Standish Group study found that over 30% of all large software projects failed to be delivered, and, of the remaining, nearly 80% failed to come in on time and budget<br />To beat these odds, and to lower the overall cost of buying software, the Department of Defense funded the Software Engineering Institute (SEI) at Carnegie Mellon University to find ways to help defense contractors build software more economically.<br />Result became the Capability Maturity Model for software, or CMM.<br />Today, the CMM/CMMI are the de facto standard for software management throughout the Federal government and is internationally recognized as a very powerful business tool and competitive differentiator.<br />
CMMI : few structural concepts<br />The SEI identified 25 total process areas and put them into the CMMI. <br />There are two ways to apply the 25 processes depending on which approach suits the development shop best. They can choose to apply pre-determined processes in a specific sequence to achieve "maturity" in managing development, or, they can choose the processes most important to their business and apply the necessary rigor to achieve a "capability" for managing development.<br />The "maturity" scale has 5 levels And, the "capability" scale has 6 levels<br />the "maturity" levels are pre-defined, the approach is called "staged." The "capability" approach is called "continuous" because the performance of the processes are tied to business objectives <br />
Case Study 1<br />GENERAL MOTORS Implementation of CMMI for acquisition <br />
Objective and Solution <br />BUSINESS CHALLENGES: GM has been acquiring and not developing IT-solutions for decades. It had to evolve constantly with changing business need. Implementation of the model required structural change and following global standard practices.<br />CMMI SOLUTION: GM recognized that it must excel in Requirements ,architecture and Project management to be a successful acquirer and customer.<br />
Implementation <br />Requirements: Acquirer ownership of requirement is essential and acquirer must be skilled in requirement engineering<br />Action: established requirement team and requirement prototyping is done<br />Architecture: Architectural philosophy varies within supplier base<br />Action: Enterprise level system engineering team built and cross area/functional architecture planning meeting held<br />Project management: better relationship with customers was necessary for the acquisition PM<br />Action: integrated GM and supplier project plan, Standard peer and acceptance review was done.<br />BENEFIT: General motors was the first commercial enterprise to be appraised utilizing CMMI- ACQ <br />The best practices encompassed in the CMMI-ACQ drove quality throughout the IT acquisition model of GM<br />
Case Study 2<br />Implementation by a leading telecom giant to improve the quality of the entire software development process<br />
Objective and Challenge <br />Objective: <br />Improve the quality of the entire software development process and ensure CMMI Level 2 process quality for all key process areas (KPAs)<br />Business Challenge:<br /><ul><li>Volatile requirements
Quality planning was also implemented along with core project metrics which were then regularly reviewed.
A new approach to configuration management procedure was proposed along with necessary templates.
Change management metrics were defined and software configuration management planning, change control, status accounting and configuration audits were implemented.</li></li></ul><li>Business Benefits<br /><ul><li>Specific pain areas identified by the client were addressed and new processes defined to address the same.
The client was assessed at CMMI Level 2 maturity after implementing and practicing the recommended process changes.
The Wipro consultants also identified gaps in the existing process with respect to CMM Level 3 requirements which helped the client in drawing up the future roadmap.</li></li></ul><li>Conclusion<br />