Limitation on Cmmi and Psp

An Overview of CMMI and PSP:

CMMI:

The CMMI is the successor of the CMM model. The Capability Maturity Model Integration for Software provides software organizations with guidance on how to gain control of their processes for developing and maintaining software and how to evolve toward a culture of software engineering and management excellence. The CMMI was designed to guide software organizations in selecting process improvement strategies by determining current process maturity and identifying the few issues most critical to software quality and process improvement. By focusing on a limited set of activities and working aggressively to achieve them, an organization can steadily improve its organization-wide software process to enable continuous and lasting gains in software process capability.

PSP:

The PSP extends the improvement process to the people who actually do the work, the practicing engineers. The PSP concentrates on the work practices of the individual engineers. The principle behind the PSP is that to produce quality software systems, every engineer who works on the system must do quality work. The PSP is designed to help software professionals consistently use sound engineering practices. It shows them how to plan and track their work, use a defined and measured process, establish measurable goals, and track performance against these goals. The PSP shows engineers how to manage quality from the beginning of the job, how to analyze the results of each job, and how to use the results to improve the process for the next project.

Limitations of CMMI and PSP:

Limitations of CMMI:

    ❖ Organisations practicing the CMMI focus too much on next level as the target, rather than improving processes. The CMMI encourages the achievement of a higher maturity level in some cases by displacing the true mission, which is improving the process and overall software quality.

    ❖ CMMI does not tell us how to achieve the goals. It describes that...