📘 Lecture 17 — CMMI Staged – Maturity Level 3 (Continue...)
📖 Overview: This lecture covers all eleven Process Areas (PAs) at CMMI Maturity Level 3, focusing on their purposes, specific goals, and specific practices. It explains how these PAs move beyond basic project management to establish organization-wide processes, proactive risk management, and formal decision-making, which are critical for predictable and mature software development.
🗂️ Topics Covered
This lecture details the eleven Process Areas for Maturity Level 3: Verification (VER) and Validation (VAL) for ensuring product quality; Organizational Process Focus (OPF), Organizational Process Definition (OPD), and Organizational Training (OT) for establishing and improving organization-wide capabilities; Integrated Project Management (IPM) for using defined, tailored processes; Risk Management (RSKM) for proactive risk handling; and Decision Analysis and Resolution (DAR) for formal decision-making. Each PA is broken down into specific goals and specific practices.
📝 Lecture Summary
PA 4 – Verification
The purpose of Verification (VER) is to ensure that selected work products meet their specified requirements. It allows the use of test setups and test simulators, which may also be used for Validation but for different purposes. Acceptance testing is mentioned here.
🔑 Definition — Verification (VER): A process area to ensure that selected work products meet their specified requirements. 📐 Formula: SG1 Prepare for Verification → SP 1.1 Select Work Products, SP 1.2 Establish Verification Environment, SP 1.3 Establish Procedures and Criteria. 📐 Formula: SG2 Perform Peer Reviews → SP 2.1 Prepare, SP 2.2 Conduct, SP 2.3 Analyze Data. 📐 Formula: SG3 Verify Selected Work Products → SP 3.1 Perform Verification, SP 3.2 Analyze Results. 📌 Example: A development team selects a specific module's code for verification. They set up a test environment with simulators, write test cases (procedures) defining expected outcomes (criteria). They then conduct a peer review with other coders to find errors, and after that, run the tests. Any failures are documented as verification results for analysis. 💡 Why this matters: Verification includes both peer reviews and testing to ensure total product coverage. Key reminders: you cannot test in quality, a peer review board is not one person, and errors found must be resolved. There are no generic practices that directly map to this process area.
PA 5 – Validation
The purpose of Validation (VAL) is to demonstrate that a product or product component fulfills its intended use when placed in its intended environment.
🔑 Definition — Validation (VAL): A process area to demonstrate that a product fulfills its intended use in its intended environment. 📐 Formula: SG1 Prepare for Validation → SP 1.1 Select Products, SP 1.2 Establish Environment, SP 1.3 Establish Procedures and Criteria. 📐 Formula: SG2 Validate Product or Product Components → SP 2.1 Perform Validation, SP 2.2 Analyze Validation Results. 📌 Example: For a new air traffic control system, the team selects the final software build for validation. They establish a test environment that mimics a real control tower, with simulated flight data. They then run the software in this environment, observing if it correctly tracks aircraft and alerts controllers as intended. Any deviations are analyzed as validation results. 💡 Why this matters: Validation is not just an end-of-project activity; it can be performed throughout the development life cycle. If a web-based system is developed and tested using the same environment and procedures users will employ, this process area might be satisfied without extra effort. There are no general practices that directly map to this process area.
PA 6 – Organizational Process Focus
The purpose of Organizational Process Focus (OPF) is to plan, implement, and deploy organizational process improvements based on a thorough understanding of the organization’s current strengths and weaknesses and its process assets. The Engineering Process Group (EPG) is introduced here as the group responsible for this.
🔑 Definition — Organizational Process Focus (OPF): A process area to plan, implement, and deploy process improvements based on understanding current processes. 🔑 Definition — Engineering Process Group (EPG): The group responsible for planning and implementing process improvement. 📐 Formula: SG1 Determine Process Improvement Opportunities → SP 1.1 Establish Needs, SP 1.2 Appraise Processes, SP 1.3 Identify Improvements. 📐 Formula: SG2 Plan and Implement Process Improvements → SP 2.1 Establish Action Plans, SP 2.2 Implement Action Plans. 📐 Formula: SG3 Deploy Process Assets and Incorporate Lessons Learned → SP 3.1 Deploy Assets, SP 3.2 Deploy Standard Processes, SP 3.3 Monitor Implementation, SP 3.4 Incorporate Experiences. 💡 Why this matters: This process area describes a cycle like the IDEAL model (Initiating, Diagnosing, Establishing, Acting, Learning). A key tip is to not try to change everything at once and to rotate EPG members after one or two years to inject new thinking. The generic practice that most closely maps is GP 3.2 Collect Improvement Information.
PA 7 – Organizational Process Definition (with IPPD)
The purpose of Organizational Process Definition (OPD) is to establish and maintain a usable set of organizational process assets and work environment standards. For IPPD, it also covers rules and guidelines for integrated teams. IPPD is applicable to specific DOD projects and is considered optional.
🔑 Definition — Organizational Process Definition (OPD): A process area to establish and maintain a usable set of organizational process assets (e.g., the Organization’s Set of Standard Processes OSSP). 📐 Formula: SG1 Establish Organizational Process Assets → SP 1.1 Establish Standard Processes, SP 1.2 Establish Life Cycle Model Descriptions, SP 1.3 Establish Tailoring Criteria and Guidelines, SP 1.4 Establish Measurement Repository, SP 1.5 Establish Process Asset Library, SP 1.6 Establish Work Environment Standards. 💡 Why this matters: A common challenge is finding the right level of detail for documenting processes—they can be too complex or too high-level. The OPD creates the OSSP, describes approved life cycles, and creates tailoring guidelines and the measurement repository. The generic practice that most closely matches is GP 3.1 Establish a Defined Process.
PA 8 – Organizational Training
The purpose of Organizational Training (OT) is to develop the skills and knowledge of people so they can perform their roles effectively and efficiently. This process area expects a Strategic Training Plan derived from the OSSP, business plans, and defined skill sets.
🔑 Definition — Organizational Training (OT): A process area to develop skills and knowledge for people to perform their roles effectively. 📐 Formula: SG1 Establish an Organizational Training Capability → SP 1.1 Establish Strategic Training Needs, SP 1.2 Determine Organizational Responsibility, SP 1.3 Establish Tactical Plan, SP 1.4 Establish Capability. 📐 Formula: SG2 Provide Necessary Training → SP 2.1 Deliver Training, SP 2.2 Establish Records, SP 2.3 Assess Effectiveness. 📌 Example: An organization identifies a strategic need to move to cloud-based development. They determine that project teams need training on AWS. A tactical plan is created for the coming year, scheduling specific AWS courses and a budget. The project plans then use this as input to schedule their team members for the training. After training, effectiveness is assessed via a test or project performance. 💡 Why this matters: This PA is about organizational training, not knowledge management (for which you would consult People CMM). Organizations must evaluate the effectiveness of training received. The generic practices that most closely match are GP 2.5 Train People (organizational view) and GP 2.2 Plan the Process (project perspective).
PA 9 – Integrated Project Management (with IPPD)
The purpose of Integrated Project Management (IPM) is to establish and manage the project and the involvement of relevant stakeholders according to an integrated and defined process that is tailored from the organization’s set of standard processes (OSSP). This PA is seen as the evolution of Project Planning (PP) and Project Monitoring and Control (PMC) from Level 2.
🔑 Definition — Integrated Project Management (IPM): A process area to manage a project using an integrated, defined process tailored from the organization’s standard processes. 🔑 Definition — Project’s Defined Process (PDP): A documented, step-by-step description of how a project will function, tailored from the OSSP. 📐 Formula: SG1 Use the Project’s Defined Process → SP 1.1 Establish the PDP, SP 1.2 Use Process Assets, SP 1.3 Establish Work Environment, SP 1.4 Integrate Plans, SP 1.5 Manage Using Integrated Plans, SP 1.6 Contribute to Process Assets. 📐 Formula: SG2 Coordinate and Collaborate with Relevant Stakeholders → SP 2.1 Manage Stakeholder Involvement, SP 2.2 Manage Dependencies, SP 2.3 Resolve Coordination Issues. 💡 Why this matters: The key difference from Level 2 management is that Level 3 uses a set of organizational plans, processes, and assets (like templates and checklists) based on best practices and lessons learned. The PDP is created by tailoring the OSSP and is then used to build the project plan. In small, non-diverse organizations, the OSSP can be used directly as the PDP. The generic practice GP 3.1 Establish a Defined Process most closely matches this PA.
PA 10 – Risk Management
The purpose of Risk Management (RSKM) is to identify potential problems before they occur so that risk-handling activities can be planned and invoked as needed. This is much more proactive than Level 2 risk management.
🔑 Definition — Risk Management (RSKM): A process area to identify potential problems proactively and plan risk-handling activities to mitigate adverse impacts. 📐 Formula: SG1 Prepare for Risk Management → SP 1.1 Determine Risk Sources and Categories, SP 1.2 Define Risk Parameters, SP 1.3 Establish a Risk Management Strategy. 📐 Formula: SG2 Identify and Analyze Risks → SP 2.1 Identify Risks, SP 2.2 Evaluate, Categorize, and Prioritize Risks. 📐 Formula: SG3 Mitigate Risks → SP 3.1 Develop Risk Mitigation Plans, SP 3.2 Implement Risk Mitigation Plans. 📌 Example: A project team defines categories like "Technical Risk" (e.g., new technology not working). They set parameters like "Probability" (1-5) and "Impact" (1-5). They identify a risk: "The new database may not handle the required load." They evaluate it with Probability=4, Impact=5, giving a priority score of 20. A mitigation plan is created: "Run a load test on a prototype within the first month." The plan is then implemented. 💡 Why this matters: This PA requires studying and measuring a risk's impact and probability. Periodic and event-driven reviews should summarize the most critical risks. Disaster recovery may be included as part of the organization's risk management culture. There are no generic practices that directly map to this process area.
PA 11 – Decision Analysis and Resolution
The purpose of Decision Analysis and Resolution (DAR) is to analyze possible decisions using a formal evaluation process that evaluates identified alternatives against established criteria.
🔑 Definition — Decision Analysis and Resolution (DAR): A process area to analyze possible decisions using a formal evaluation process with established criteria. 📐 Formula: SG1 Evaluate Alternatives → SP 1.1 Establish Guidelines for Decision Analysis, SP 1.2 Establish Evaluation Criteria, SP 1.3 Identify Alternative Solutions, SP 1.4 Select Evaluation Methods, SP 1.5 Evaluate Alternatives, SP 1.6 Select Solutions. 📌 Example: A project must choose a new code editor. They establish guidelines that DAR must be used for purchases over $1000. They create evaluation criteria: cost, features, ease of use (weighted). They identify alternatives: Editor A, B, and C. They select a method (e.g., weighted scoring matrix). They evaluate each editor against the criteria, then select the highest-scoring solution. 💡 Why this matters: The organization must define when this PA should be used to avoid overuse or underuse. All changes to evaluation criteria must be documented, including the reason, who initiated it, and the impact. There are no generic practices that directly map to this process area.
⭐ Key Takeaways
This lecture covers the eleven Process Areas of CMMI Maturity Level 3, which moves an organization from project-specific management to organization-wide process standardization. The Engineering PAs (Verification & Validation) ensure product quality through both peer reviews and testing in simulated or actual environments. The Process Management PAs (OPF, OPD, OT) establish the infrastructure for continuous process improvement, including creating a standard process library and providing strategic training. The Project Management PAs (IPM, RSKM) evolve Level 2 concepts by requiring defined, tailored processes for each project and proactive, quantified risk management. Finally, the Support PA (DAR) ensures that critical decisions are made formally and objectively using established criteria and alternatives.
🧠 Quick Revision Questions
- What is the main difference between Verification (VER) and Validation (VAL) according to this lecture?
- What is the role of the Engineering Process Group (EPG) mentioned in the Organizational Process Focus (OPF) process area?
- How does Integrated Project Management (IPM) differ from Level 2 Project Planning (PP)?
- What is a key requirement for using the Decision Analysis and Resolution (DAR) process area effectively in an organization?
- Why is it important to review risks periodically during a project, even if no new risks are identified?
📘 Lecture 18 — CMMI Staged – Maturity Level 4
📖 Overview: This lecture explores CMMI Maturity Level 4, where organizations manage processes "by the numbers" using quantitative data and statistical control. It details the two key process areas — Organizational Process Performance and Quantitative Project Management — and how they build upon Levels 2 and 3. The lecture also introduces Level 5 concepts, focusing on continuous process improvement through Organizational Innovation and Deployment and Causal Analysis and Resolution.
🗂️ Topics Covered
This lecture covers the concept of Level 4 maturity as a quantitatively managed plateau where organizational decisions are driven by numerical data. It explains the Organizational Process Performance (OPP) process area, which establishes performance baselines and models, and the Quantitative Project Management (QPM) process area, which manages projects against quantitative objectives. The lecture then moves to Level 5, covering Organizational Innovation and Deployment (OID) for selecting and deploying process improvements, and Causal Analysis and Resolution (CAR) for identifying and preventing root causes of defects.
📝 Lecture Summary
Staged Representation
The staged representation is the approach used in the Software CMM, using predefined sets of process areas to define an improvement path for an organization. This improvement path is described by a model component called a maturity level, which is a well-defined evolutionary plateau toward achieving improved organizational processes.
Level 4
Level 4 is all about numbers. Projects are managed "by the numbers," organizational decisions are made "by the numbers," and processes, services, and product quality are all measured "by the numbers." At Level 4, the organization has achieved all of the goals of Levels 2 and 3. Processes, although qualitatively stable and predictable at Level 3, can be proved to be quantitatively stable and predictable at Level 4. Level 4 analyzes the data collected, determines special causes of variation from the norm, and supports quantitative management and control. This is done to make your processes predictable.
To get "good" data, an organization usually has to collect data for several years, or at least through several projects and several life cycles of the projects. When you first begin collecting data, it will not be consistent. Measurements data are collected beginning with Level 2 in the staged representation, but the data are not clean and consistent because the processes used on the projects are not yet stable and consistent. An organization cannot go to Level 4 overnight.
At Level 3, measures are collected and preliminary thresholds are established, usually relating to size and effort. At Level 4, the control limits are based on years of historical data and trends analyses. More data are collected, and more limits are established, monitored, and refined. At Level 3, the data may be somewhat inconsistent and "dirty," whereas Level 4 expects stabilized, normalized, statistically accurate data.
Process Areas at Level 4
There are no additions to the list of generic goals at Level 4 from Level 3. What makes this maturity level different are the two process areas: Organizational Process Performance and Quantitative Project Management. To satisfy the goals for Level 4, the goals for Levels 2 and 3 must be satisfied as well, both for specific goals and generic goals (GG2 Institutionalize a Managed Process and GG3 Institutionalize a Defined Process).
PA 1 – Organizational Process Performance
The purpose of Organizational Process Performance (OPP) is to establish and maintain a quantitative understanding of the performance of the Organization’s Set of Standard Processes (OSSP) in support of quality and process–performance objectives, and to provide the process–performance data, baselines, and models to quantitatively manage the organization’s projects.
- Specific Goal for Level 4: SG1 Establish Performance Baselines and Models
- Specific Practices: SP 1.1 Select Processes; SP 1.2 Establish Process–performance Measures; SP 1.3 Establish Quality and Process–performance Objectives; SP 1.4 Establish Process–performance Baselines; SP 1.5 Establish Process–performance Models
This process area includes measurements for both process and product, and service has also been specifically presented as an area appropriate for measurement. A process performance baseline (PPB) documents the historical results achieved by following a process and is used as a benchmark for comparing actual process performance against expected process performance. A process performance model (PPM) describes the relationships among attributes (for example, defects) of a process and its work products. A PPM is used to estimate or predict a critical value that cannot be measured until later in the project’s life.
The most common measurements used are size, effort, cost, schedule, and product defect density. Performance-related measurements can include schedule variance (lateness), effort variance, and unplanned tasks. Quality-related measurements may include rework and defects collected during all life-cycle phases. Common process-related measures are related to productivity at different phases of life cycles.
🔑 Definition — Process Performance Baseline (PPB): Documents the historical results achieved by following a process. It is used as a benchmark for comparing actual process performance against expected process performance. 🔑 Definition — Process Performance Model (PPM): Describes the relationships among attributes of a process and its work products. It is used to estimate or predict a critical value that cannot be measured until later in the project’s life. 📌 Example: At Level 3, measures are collected in a database per project. In Level 2, measures bubble up to an organizational database. At Level 3, data are reviewed for consistency and accuracy. Then at Level 4, statistically-based controls are applied.
Things People Forget: The organization either builds too many models or not enough. Nobody really understands the models that are built (except maybe the person who built them). The models aren’t really used to make decisions.
PA 2 – Quantitative Project Management
The purpose of Quantitative Project Management (QPM) is to quantitatively manage the project’s defined process to achieve the project’s established quality and process–performance objectives.
- Specific Goals: SG1 Quantitatively Manage the Project; SG2 Statistically Manage Sub-process Performance
- Specific Practices (SG1): SP 1.1 Establish the Project’s Objectives; SP 1.2 Compose the Defined Process; SP 1.3 Select the Sub-processes That Will Be Statistically Managed; SP 1.4 Manage Project Performance
- Specific Practices (SG2): SP 2.1 Select Measures and Analytic Techniques; SP 2.2 Apply Statistical Methods to Understand Variation; SP 2.3 Monitor Performance of the Selected Sub-processes; SP 2.4 Record Statistical Management Data
In this process area, usage of the organizational level measurement repository is refined. Experienced managers and measurement personnel identify measures, senior level project personnel collect the measures, and projects use the measures. Project managers should do at least a weekly review of the project measures. Repositories require years of historical data using the same, normalized data, with reviews and analyses of these data.
💡 Why this matters: Level 4 is where senior management commitment and participation really come to the fore. Business decisions are supposed to be made based on the numbers. Most small organizations will find this level very difficult to implement due to the number of people needed and the type of expertise required.
Things People Forget: Make sure the project manager (or whoever will use these data) is involved in determining which measures are needed. Train both the people collecting data and those who will use it. Show how the project’s defined process was changed, reviewed, or influenced by these data.
CMMI Staged – Maturity Level 5
At Level 5, an organization has achieved all of the goals of Levels 2, 3, and 4. The major difference between Level 4 and Level 5 is that Level 4 analyzes data for special causes of variation, while Level 5 addresses common causes of variation. Level 5 concentrates on improving the overall quality of the organization’s processes by:
- Identifying common causes of variation
- Determining root causes of the conditions identified
- Piloting process improvements
- Incorporating improvements into the OSSP
Although innovative, radical approaches to introduce change are often undertaken, most organizations have found that an incremental approach works better and has longer-lasting results.
- Process Areas at Level 5: Organizational Innovation and Deployment; Causal Analysis and Resolution
- No additions to generic goals at Level 5 from Level 3.
PA 1 – Organizational Innovation and Deployment
The purpose of Organizational Innovation and Deployment (OID) is to select and deploy incremental and innovative improvements that measurably improve the organization’s processes and technologies. The improvements support the organization’s quality and process–performance objectives as derived from the organization’s business objectives.
- Specific Goals: SG1 Select Improvements; SG2 Deploy Improvements
- SG1 Specific Practices: SP 1.1 Collect and Analyze Improvement Proposals; SP 1.2 Identify and Analyze Innovations; SP 1.3 Pilot Improvements; SP 1.4 Select Improvements for Deployment
- SG2 Specific Practices: SP 2.1 Plan the Deployment; SP 2.2 Manage the Deployment; SP 2.3 Measure Improvement Effects
In OID, proposals are subjected to quantitative analysis. Metrics from the historical database, as well as defects and where they were introduced, are reviewed to determine where and how to make improvements. Steps include submitting proposals, analyzing them (including cost-benefit review), piloting the improvement, measuring effectiveness, planning deployment, deploying, and measuring effectiveness across the organization.
Things People Forget: You must pilot your improvement! Only piloting can accurately predict whether an improvement will work. Many organizations skip this step, which is a wrong approach.
PA 2 – Causal Analysis and Resolution
The purpose of Causal Analysis and Resolution (CAR) is to identify causes of defects and other problems and take action to prevent them from occurring in the future.
- Specific Goals: SG1 Determine Causes of Defects; SG2 Address Causes of Defects
- SG1 Specific Practices: SP 1.1 Select Defect Data for Analysis; SP 1.2 Analyze Causes
- SG2 Specific Practices: SP 2.1 Implement the Action Proposals; SP 2.2 Evaluate the Effect of Changes; SP 2.3 Record Data
This process area looks at defects and determines their root cause — the most basic reason why the defect occurred, such that if that cause is removed, the defect vanishes. Steps include looking at defects and problems, selecting data to analyze, analyzing causes, preparing proposals to address problems, implementing proposals, and evaluating the effects of changes.
Things People Forget: You are analyzing defects of the process. The defects of the process may result in product defects. The processes under review should be quantitatively managed processes — those studied and implemented using Level 4 concepts.
🔑 Definition — Root Cause: The most basic reason why a defect occurred (or the source of the defect). If that cause is removed, the defect vanishes.
Summary of Level 5
The focus at Level 5 is on improving processes using the OSSP as the controlling document. Level 5 tries to find common causes and fix them, resulting in overall improvements. Measurements are used to select improvements, estimate costs and benefits, and prove actual results. There are two types of improvement strategies: innovative (introducing radical changes) and incremental (building on earlier improvements). Incremental approaches tend to have more long-lasting effects and lead to easier institutionalization.
⭐ Key Takeaways
Maturity Level 4 is about quantitative management "by the numbers," requiring years of stable, consistent historical data to establish control limits, baselines, and models. The two key process areas are Organizational Process Performance (establishing PPBs and PPMs) and Quantitative Project Management (statistically managing sub-processes). Level 5 extends this by addressing common causes of variation through Organizational Innovation and Deployment (piloting improvements before deployment) and Causal Analysis and Resolution (finding and eliminating root causes of defects). Organizations must progress sequentially through maturity levels, as Level 4 requires stable processes from Level 3, and Level 5 requires quantitative processes from Level 4. Most organizations find incremental, piloted improvements more effective than radical approaches.
🧠 Quick Revision Questions
- What is the key difference between Level 3 and Level 4 regarding process stability?
- What are the two process areas at CMMI Level 4, and what is the purpose of each?
- What is a Process Performance Baseline (PPB) and a Process Performance Model (PPM)?
- What distinguishes Level 5 from Level 4 in terms of variation analysis?
- Why is piloting improvements considered essential in the Organizational Innovation and Deployment process area?
📘 Lecture 19 — Introduction to CMMI Continuous Representation
📖 Overview: This lecture introduces the CMMI Continuous Representation, a process improvement approach that allows organizations to focus on specific process areas. It covers the structure of the model, including process area categories, capability levels, and how goals and practices are organized. This is crucial for understanding how to tailor process improvement to an organization's specific needs.
🗂️ Topics Covered
The lecture covers the fundamental concepts of the CMMI Continuous Representation, including its model components, the Process Area Categories (Process Management, Project Management, Engineering, Support), the relationship between specific and generic goals and practices, the definition and description of six capability levels (0 to 5), process area capability profiles, target profiles, and the cumulative nature of capability levels.
📝 Lecture Summary
Continuous Representation
The continuous representation is an approach that allows an organization to select a specific process area and improve relative to it, rather than improving all process areas at once. This approach uses capability levels to characterize improvement relative to an individual process area.
🔑 Definition — Continuous Representation: An approach to process improvement that allows an organization to select a specific process area and improve it to a defined capability level.
CMMI Model Components in the Continuous Representation
The continuous representation has specific goals that organize specific practices and generic goals that organize generic practices. Each specific and generic practice corresponds to a capability level. Specific goals and specific practices apply to individual process areas. While using the same basic structure as the staged representation, each Process Area (PA) belongs to a Process Area Category, which is a simple way of arranging PAs by their related, primary functions.
Process Area Categories
There are four process area categories:
- Process Management: PAs consist of common functions related to defining, planning, implementing, and monitoring a process. They all reside at the organizational level and are listed in increasing order of sophistication.
- Project Management: PAs consist of functions related to planning, tracking, and controlling projects, and are listed in increasing order of sophistication.
- Engineering: PAs consist of technical functions related to building and delivering a product, and are listed in increasing order of sophistication.
- Support: PAs consist of related support functions related to managing changes, ensuring quality, measuring results, and structured decision-making.
💡 Why this matters: These categories help an organization group related processes and focus improvement efforts on specific business functions.
Goals and Practices
Specific goals and practices relate to specific process areas and to tasks that make sense for that process area only. Generic goals and practices relate to multiple process areas. For example, to achieve Capability Level 2 for Requirements Management, an organization must also establish an organizational policy, plan the process, and train people. Both specific and generic goals must be satisfied to achieve a capability level. Each capability level has one generic goal associated with it.
Generic Goals and Practices
Each Generic Goal (GG) and its associated Generic Practices (GPs) are defined:
- Generic Goal 1: Achieve Specific Goals of Each Process Area
- Generic Practice GP 1.1: Perform Specific Practices
- Generic Goal 2: Institutionalize a Managed Process
- Generic Practices GP 2.1 – 2.10: Cover activities like establishing policy (Project Planning), planning (Project Planning), training (Organizational Training), and monitoring (Project Monitoring and Control).
- Generic Goal 3: Institutionalize a Defined Process
- Generic Practices GP 3.1 & 3.2: Focus on establishing a defined process (Integrated Project Management) and collecting improvement information (Integrated Project Management, Organizational Process Focus).
- Generic Goal 4: Institutionalize a Quantitatively Managed Process
- Generic Practices GP 4.1 & 4.2: Involve establishing quantitative objectives (Quantitative Project Management, Organizational Process Performance) and stabilizing sub-process performance (Quantitative Project Management, Organizational Process Performance).
- Generic Goal 5: Institutionalize an Optimizing Process
- Generic Practices GP 5.1 & 5.2: Focus on continuous process improvement (Organizational Innovation and Deployment) and correcting root causes (Causal Analysis and Resolution).
Continuous Representation vs. Staged
The continuous representation has the same basic information as the staged representation, but arranged differently using capability levels and process area categories. It focuses process improvement on actions to be completed within process areas.
What is a Capability Level?
A Capability Level focuses on maturing an organization's ability to perform, control, and improve its performance in a specific process area. This allows the organization to focus improvement efforts where they are most needed.
🔑 Definition — Capability Level: A measure of how well an organization performs a specific process area, ranging from Incomplete (Level 0) to Optimizing (Level 5).
Capability Levels
There are six capability levels:
- Level 0: Incomplete: An incomplete process does not implement all of the Capability Level 1 specific practices. It’s similar to Maturity Level 1 in staged representation.
- Level 1: Performed: A Capability Level 1 process performs all of the Capability Level 1 specific practices. Performance may not be stable, but useful work can be done.
- Level 2: Managed: A managed process is planned, performed, monitored, and controlled for individual projects. It ensures the process achieves its objectives, including cost, schedule, and quality.
- Level 3: Defined: A defined process is a managed process that is tailored from the organization's set of standard processes. Deviations outside of tailoring guidelines are documented, justified, reviewed, and approved.
- Level 4: Quantitatively Managed: A quantitatively managed process is a defined process controlled using statistical and other quantitative techniques. Product quality and process performance are understood in statistical terms.
- Level 5: Optimizing: An optimizing process is a quantitatively managed process that is improved based on an understanding of the common causes of process variation. It focuses on continually improving through both incremental and innovative improvements.
💡 Why this matters: Capability levels allow an organization to precisely track its progress in mastering a specific process area.
Process Area Capability Profile
A process area capability profile can be represented by a set of points in two dimensions:
- The Process Dimension: Describes what you do (the process areas selected).
- The Capability Dimension: Describes how well you do it (the capability levels achieved).
Target Profile
A target profile is a list of process areas and their corresponding capability levels that an organization aims to achieve. Target staging is a sequence of target profiles that describes the path of process improvement an organization will take.
🔑 Definition — Target Profile: A list of process areas and the capability levels an organization aims to achieve for each.
Achievement Profile
An achievement profile is used in the continuous representation. It is a bar chart of each process area that shows how much of the PA has been achieved and how much has not.
🔑 Definition — Achievement Profile: A visual representation (bar chart) of each process area showing the capability level achieved.
Generic Practices Relating to Process Areas
Generic practices are used to determine if generic goals have been satisfied. An organization using the continuous representation must satisfy the basic concepts of Maturity Level 2 (i.e., planning, managing changes) for every process area they select. The continuous representation was designed to tailor the model and process improvement approaches focusing on specific categories that match areas where problems exist.
⭐ Key Takeaways
The key takeaway is that the continuous representation allows organizations to focus on improving specific process areas using capability levels, unlike the staged representation which requires an organization to improve all process areas to a certain maturity level. The model is organized into four process area categories—Process Management, Project Management, Engineering, and Support—which help group related functions. Both specific and generic goals must be met to achieve a capability level, and importantly, generic practices for lower levels (like planning and monitoring) must be addressed even if the corresponding process area wasn't selected. Target and achievement profiles are essential tools for planning and tracking progress in a continuous representation improvement path.
🧠 Quick Revision Questions
- What is the main difference between the CMMI Continuous and Staged representations?
- Name the four Process Area Categories in the Continuous Representation.
- Explain the difference between a Specific Goal and a Generic Goal in CMMI.
- List the six capability levels from 0 to 5.
- What is a Target Profile, and how is it used in process improvement?
📘 Lecture 20 — Personal Software Process (PSP)
📖 Overview: This lecture introduces the Personal Software Process (PSP), a defined and measured software process designed for use by individual software engineers. Developed by Watts Humphrey at the SEI, PSP scales down CMM principles to the personal level, addressing critical business needs for better cost/schedule management, quality improvement, and reduced cycle time. The lecture explains how PSP empowers engineers to take ownership of their process through measurement, planning, and quantitative feedback.
🗂️ Topics Covered
The lecture covers the concept and definition of PSP, its role in cost and schedule management, quality management, cycle time reduction, and organizational process improvement. It provides background on why software businesses need PSP, explains how PSP works, lists the 12 CMM Key Process Areas adapted for PSP, summarizes PSP in a nutshell, and describes the personal improvement process cycle.
📝 Lecture Summary
Concept of PSP
Many viewed the CMM as designed for large organizations and did not see how it could be applied to individual work or small project teams. The SEI started a process research project to examine ways individual software engineers could apply level-5 process principles. After several years of research, means were devised to adapt 12 of the 18 CMM key process areas to the work of individual software engineers.
💡 Why this matters: This shows that high-maturity process principles are not just for large organizations; they can be scaled down for individual use.
What is PSP?
The PSP is a defined and measured software process designed to be used by an individual software engineer. It was developed by Watts Humphrey. Its intended use is to guide the planning and development of software modules or small programs, but it is adaptable to other personal tasks.
🔑 Definition — Personal Software Process (PSP): A defined and measured software process for individual software engineers, based on CMM principles, to guide planning and development.
PSP
Like the SEI Capability Maturity Model for Software (CMM-SW), the PSP is based on process improvement principles. While the CMM-SW focused on improving organizational capability, the focus of the PSP is the individual engineer. To foster improvement at the personal level, PSP extends process management and control to the software engineer. With PSP, engineers develop software using a disciplined, structured approach. Individual engineers follow a defined process, plan, measure, and track their work, manage product quality, and apply quantitative feedback to improve their personal work processes, leading to:
- better estimating
- better planning and tracking
- protection against over-commitment
- a personal commitment to quality
- the engineer's involvement in continuous process improvement
Thus, both the individual and the organization's capability are improved.
Cost and Schedule Management
A critical business need for all organizations that develop software is better cost and schedule management. Cost and schedule problems often begin when projects make commitments that are based on inadequate estimates of size and development resources. PSP addresses this problem by showing engineers how to make better size and resource estimates using statistical techniques and historical data. A more balanced estimation error means that the errors tend to cancel, rather than compound, when multiple estimates are combined.
Quality Management
A second critical business need is for improved software quality. Poor quality management now limits our ability to field many critical systems, increases software development costs, and makes development schedules even harder to predict. Many of these quality problems stem from the practice of relying on testing to manage software quality. But finding and fixing defects in test is costly, ineffective, and unpredictable. The most efficient and effective way to manage software quality is through a comprehensive program focused on removing defects early, at the source. The PSP helps engineers to find and remove defects where they are injected, before compile, inspection, unit test, integration test, or system test. With fewer defects to find and remove in integration and system test, test costs are reduced sharply, schedules are more predictable, fewer defects are released to the field, maintenance and repair costs are reduced, and customer satisfaction is increased.
🔑 Definition — Early Defect Removal: The practice of finding and fixing defects at the point they are injected, before later development phases like compile or test.
Cycle Time
A third critical business need is for reduced product cycle time. Cycle time can be reduced through better planning and the elimination of rework through improvements in product quality. Accurate plans allow for tighter scheduling and greater concurrency among planned activities. Better quality through early defect removal reduces waste and further increases planning accuracy by reducing a source of variation, the discovery and repair of defects in integration and system test. With PSP, engineers learn how to gather the process data needed to minimize cycle time. The data helps them to build accurate plans, eliminate rework, and reduce integration and system test by as much as four to five times.
Organizational Process Improvement
A fourth critical business need is process improvement. It is well understood that process improvement can increase competitive advantage, but it has been difficult to involve software engineers. They often view process improvement and product quality as a management or staff activity, not as their personal responsibility. With PSP, engineers gain personal experience with process improvement. They become process owners, directly involved in the measurement, management, and improvement of the software process.
Background and Introduction
All businesses are becoming software businesses. More and more businesses now develop and incorporate software in the products they produce, or develop software to support the design, manufacture, or delivery of the products and services they provide. Many are finding that as the software component of their business grows, schedule delays, cost overruns, and quality problems caused by software are becoming their number one business problem. Software development has become the high-risk element in their business plans. Moreover, despite their best management efforts, they find their risk of failure increasing with each increase in the size or complexity of the software they produce. Software businesses have at least one thing in common: the business is dependent on people. Software products are made of hundreds to millions of individual computer instructions, each one handcrafted by a software engineer. And so, the technical practices and experience of their engineers largely determine the outcome of the development process. Software businesses also share a common set of needs: better cost and schedule management, improved software quality, and reduced software development cycle time. PSP directly addresses these needs by improving the technical practices and individual abilities of software engineers, and by providing a quantitative basis for managing the development process. By improving individual performance, PSP can improve the performance of the organization, as individual improvements in aggregate are reflected at the organizational level.
How
Data from the PSP improve planning and tracking of software projects. Early defect removal results in higher quality products, as well as reductions in test costs and cycle time. PSP provides a classroom setting for learning and practicing process improvement. Short feedback cycles and personal data make it easier to gain understanding through experience. PSP helps engineers and their managers learn to practice quantitative process management. They learn to use defined processes and collect data to manage, control, and improve the work. Finally, PSP exposes engineers to 12 of the CMM Key Process Areas (KPAs). They are better prepared to participate in CMM-based improvement. The PSP provides a framework for teaching engineers about the software process, and a starting point from which they can evolve their own personal processes. The PSP is based on the same industrial practices that are found in the SEI CMM, but scaled-down for individual use. It is a defined and measured, individualized process for consistently and efficiently developing high quality software modules or small programs. It has been adapted to many other kinds of software engineering tasks, such as developing software requirements, software specifications, and test cases. The PSP can also be scaled up to support small projects by integrating individual personal processes with a project process that was based on the PSP architecture. In general, once learned, the principles and concepts in the PSP can be applied to any structured, repetitive task.
Key Process Areas for PSP
The 12 CMM Key Process Areas (KPAs) adapted for PSP are:
- Software project planning
- Software project tracking/oversight
- Software process focus
- Software process definition
- Integrated software management
- Software product engineering
- Peer reviews
- Quantitative process management
- Quality management
- Defect prevention
- Technology change management
- Process change management
PSP in a Nutshell
PSP in a nutshell involves:
- Baselining your existing personal software process
- Developing a planning process for your software development
- Measuring software size as part of the planning process
- Estimating software size in advance
- Estimating the required schedule and resources for software
- Conducting appropriate measures of one's process
- Conducting meaningful design and code reviews
- Performing software quality management
- Perform software design in a more formal fashion
- Verifying the design, using methods such as object state machines, program tracing, etc.
- Scaling up the PSP to larger problems
Personal Improvement Process
The personal improvement process cycle consists of:
- Define the quality goals
- Measure product quality
- Understand the process
- Adjust the process
- Use the adjusted process
- Measure the results
- Compare the results with the goal
⭐ Key Takeaways
The PSP is a scaled-down, individualized application of CMM principles for software engineers to improve their personal performance. It addresses critical business needs by directly improving cost/schedule estimation through statistical techniques and historical data, and by promoting early defect removal to enhance quality and reduce cycle time. Engineers become process owners, not just followers, by using defined processes and collecting personal data for quantitative process management. The PSP framework exposes engineers to 12 CMM KPAs and follows a cyclic personal improvement process of defining goals, measuring, understanding, adjusting, and comparing results. Ultimately, improving individual performance through PSP aggregates to improve organizational capability.
🧠 Quick Revision Questions
- What is the Personal Software Process (PSP) and who developed it?
- List three critical business needs that PSP directly addresses.
- How does PSP help improve cost and schedule management?
- What is the key strategy for quality management in PSP, and why is it effective?
- Name the steps in the personal improvement process cycle.