Presentation is loading. Please wait.

Presentation is loading. Please wait.

CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.

Similar presentations


Presentation on theme: "CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual."— Presentation transcript:

1 CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual effort and heroics. 2.Repeatable - Basic project management processes are established to track cost, schedule, and functionality. The necessary process discipline is in place to repeat earlier successes on projects with similar applications. 3.Defined - The software process for both management and engineering activities is documented, standardized, and integrated into a standard software process for the organization. All projects use an approved, tailored version of the organization's standard software process for developing and maintaining software. 4.Managed - Detailed measures of the software process and product quality are collected. Both the software process and products are quantitatively understood and controlled. 5.Optimizing - Continuous process improvement is enabled by quantitative feedback from the process and from piloting innovative ideas and technologies. CMMI or the Capability Maturity Model is a method for evaluating and measuring the maturity of software development process of organizations on a scale from 1 to 5. The CMMI doesn’t tell the companies how to implement, but it tells what to implement. The way of implementation is left for each organization to determine, and the assessment method supports this idea. One of the main problems that face most of the organizations that attempt to improve is often to find themselves juggling many improvements initiatives. As CMMI has become more widely known as the most famous software quality framework and Six Sigma has made its way into engineering disciplines, the point of concern is: do they conflict, can they work together, Isn't Six Sigma only about advanced statistics, how can it help in software process improvement? The typical answer would be CMMI L4 is about advanced statistics! At CMMI L5, the organization, uses the analyzed data, perform root causes for the discovered problems, improve the process to correct the deficiencies, improve and control the capability of the process. The practices of this level can be incorporated in the Analyze, Improve and Control phases of the Six Sigma.

2 CMMI 1.At the Optimizing Level or the CMM level5, the entire organization is focused on continuous Quantitative feedback from previous projects is used to improve the project management, usually using pilot projects, using the skills shown in level 4. The focus is on continuous process improvement. 2.Software project teams in Level 5 organizations Analyze defects to determine their causes. Software processes are evaluated to prevent known types of defects from recurring. Lessons learned are disseminated to other projects. 3.The software process capability of Level 5 organizations can be characterized as continuously improving because Level 5 organizations are continuously striving to improve the range of their process capability, thereby improving the process performance of their projects. Improvement occurs both by incremental advancements in the existing process and by innovations using new technologies and methods.


Download ppt "CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual."

Similar presentations


Ads by Google