📘 Lecture 14 — Introduction to CMMI Staged Representation
📖 Overview: This lecture introduces the CMMI staged representation, an approach that uses predefined sets of process areas organized by maturity levels to define an improvement path for an organization. It explains the five maturity levels, the structure of the model including process areas, goals, and practices, and emphasizes that maturity levels cannot be skipped. This matters because it provides a systematic, step-by-step framework for organizations to progressively improve their processes.
🗂️ Topics Covered
This lecture covers the concept of staged representation and how it differs from continuous representation (not covered here). It details the five maturity levels (Performed, Managed, Defined, Quantitatively Managed, Optimizing), explaining the focus and characteristics of each level. The structure of CMMI staged representation is broken down into process areas, goals (specific and generic), practices (specific and generic), and common features (Commitment to Perform, Ability to Perform, Directing Implementation, Verification). It also discusses the rule that maturity levels cannot be skipped and provides examples of process areas for each level.
📝 Lecture Summary
Staged Representation
The staged representation is an approach that uses 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. The staged representation offers a systematic, structured way to approach process improvement one step at a time. Achieving each stage ensures that an adequate foundation has been laid as a foundation for the next stage. Process areas are organized by maturity levels, prescribing the order for implementing each process area according to maturity levels, which define the improvement path for an organization from the initial level to the optimizing level.
Maturity Levels
Achieving each maturity level ensures that an adequate improvement foundation has been laid for the next maturity level and allows for lasting, incremental improvement. A maturity level signifies the level of performance that can be expected from an organization. There are five maturity levels, each a layer in the foundation for continuous process improvement: Performed, Managed, Defined, Quantitatively Managed, and Optimizing.
💡 Why this matters: Maturity levels provide a clear roadmap for improvement, ensuring that lower-level discipline is established before more advanced process innovations are attempted.
Structure of the CMMI Staged Representation
- Commitment to Perform: creates policies and secures sponsorship for process improvement efforts.
- Ability to Perform: ensures that the project and/or organization has the resources it needs to pursue process improvement.
- Directing Implementation: collects, measures, and analyzes data related to processes.
- Verification: verifies that the projects and/or organization's activities conform to requirements, processes, and procedures.
- All old common features got rolled into Level 2 generic practices. Both activities and common features are present in each Key Process Area (KPA), where the common features include Commitment to Perform, Ability to Perform, Measurement and Analysis, and Verifying Implementation.
Maturity Levels Cannot Be Skipped
A level provides a necessary foundation for effective implementation of processes at the next level.
- Higher level processes are easily sacrificed without the discipline provided by lower levels.
- The effect of innovation is obscured in a noisy process.
- Higher maturity level processes may be performed by organizations at lower maturity levels, with the risk of not being consistently applied in a crisis.
Process Areas
Process Areas (PAs) are clusters of related practices performed collectively to achieve a set of goals. They are the major building blocks in establishing the process capability of an organization. Each process area has been defined to reside at a given maturity level.
Process Areas by Maturity Level
| Level | Focus | Process Areas |
|---|---|---|
| 5 Optimizing | Continuous process improvement | Organizational Innovation and Deployment; Causal Analysis and Resolution |
| 4 Quantitatively Managed | Quantitative management | Organizational Process Performance; Quantitative Project Management |
| 3 Defined | Process standardization | Requirements Development; Technical Solution; Product Integration; Verification; Validation; Organizational Process Focus; Organizational Process Definition; Organizational Training; Integrated Project Management; Risk Management; Decision Analysis and Resolution |
| 2 Managed | Basic Project management | Requirements Management; Project Planning; Project Monitoring and Control; Supplier Agreement Management; Measurement and Analysis; Process and Product Quality Assurance; Configuration Management |
Level 1: Performed
(No specific characteristics or process areas are detailed for this level in the lecture; it is the initial starting point.)
Level 2: Managed
Characteristics of a Level 2 organization include:
- Adhering to organizational policies
- Following a documented plan and process description
- Applying adequate funding and resources
- Maintaining appropriate assignment of responsibility and authority
- Training people in their appropriate processes
- Placing work products under appropriate configuration management
- Monitoring and controlling process performance, and taking corrective action
- Objectively reviewing the process, work products, and services, and addressing noncompliance
- Reviewing the activities, status, and results of the process with appropriate levels of management, and taking corrective action
- Identifying and interacting with relevant stakeholders
Level 3: Defined
At Level 3, the organization has achieved all of the goals of Level 2. There is an organizational way of doing business, with tailoring of this organizational method allowed under predefined conditions. The organization has an Organization's Set of Standard Processes (OSSP). The following characteristics of the process are clearly stated: Purpose, Inputs, Entry criteria, Activities, Roles, Measures, Verification steps, Outputs, Exit criteria. Level 3 continues with defining a strong, meaningful, organization-wide approach to developing products. An important distinction between Level 2 and Level 3 is that at Level 3, processes are described in more detail and more rigorously than at Level 2. Processes are managed more proactively, based on a more sophisticated understanding of the interrelationships and measurements of the processes and parts of the processes. Level 3 is more sophisticated, more organized, and establishes an organizational identity—a way of doing business particular to this organization.
Level 4: Quantitatively Managed
For Maturity Level 4, the organization has achieved all of the goals of Levels 2 and 3. The organization controls its processes by statistical and other quantitative techniques. Product quality, process performance, and service quality are understood in statistical terms and are managed throughout the life of the processes. Level 4 focuses on using metrics to make decisions and to truly measure whether progress is occurring and your product is improving. Distinctions between Level 3 and Level 4 are that at Level 3, processes are qualitatively predictable, while at Level 4, processes are quantitatively predictable. Level 4 addresses special causes of process variation and takes corrective action.
Level 5: Optimizing
At Level 5, the organization has achieved all of the goals of Levels 2, 3, and 4. Processes are continually improved based on an understanding of common causes of variation within the processes. Level 5 is described as "nirvana": everyone is a productive member of the team, defects are reduced, and your product is delivered on time and within the estimated budget.
🔑 Definition — Maturity Level: A well-defined evolutionary plateau on the path to becoming a mature organization, signifying the level of performance that can be expected from an organization.
Maturity Levels (Reiteration on Process Boundaries)
In the staged representation, the maturity levels serve as process boundaries—meaning that the efforts documented in that maturity level relate only to that maturity level. For example, Requirements Management is a Level 2 process area. To be considered a Maturity Level 2 organization, the projects undergoing process improvement need to satisfy the goals for all of the process areas for Maturity Level 2. An organization seeking to be Maturity Level 3 would need to structure their process improvement program to satisfy the goals for both Level 2 and Level 3. The process areas listed in Level 2 are not listed in Level 3, and vice versa. The same holds true for Maturity Level 4 and Maturity Level 5. You must satisfy all of the goals in the previous levels plus the goals for the current level in order to attain the maturity level rating. Each maturity level consists of process areas. Each process area contains goals that must be satisfied. Each goal has certain practices or actions associated with it.
Process Areas (Reiteration)
Each maturity level consists of several process areas. A process area is a group of practices or activities performed collectively in order to achieve a specific objective.
Goals
Each PA has several goals that need to be satisfied in order to satisfy the objectives of the PA. There are two types of goals:
- Specific Goals (SG): goals that relate only to the specific PA under study.
- Generic Goals (GG): goals that are common to multiple process areas throughout the model. These goals help determine whether the PA has been institutionalized.
🔑 Definition — Institutionalized: Embedded in the way the organization does its business, making it effective, repeatable, and lasting.
Practices
Practices are activities that must be performed to satisfy the goals for each PA. Each practice relates to only one goal. There are two types of practices:
- Specific Practices (SP): practices that relate to specific goals.
- Generic Practices (GP): practices associated with the generic goals for institutionalization.
Example: Specific Goal and Specific Practice
- Specific Goal (from Requirements Management PA): Requirements are maintained and accurately reflected in project plans, activities and products.
- Specific Practice (from Requirements Management PA): Maintain the traceability of requirements to their source requirements.
- Generic Goal (from Maturity Level 2): Institutionalize a Managed Process.
- Generic Practice (from Maturity Level 2): Establish an Organizational Policy.
Common Features
Common features are a means of categorizing Generic practices.
- Commitment to perform: establishment of management policies.
- Ability to perform: establishment and maintenance of plans, resources, assigned responsibility and authority, and training.
- Directing implementation: measurement, control, and performance practices.
- Verification: ensure implementation and compliance.
Another way to look at Common Features
Common feature categories are very similar across process areas. They are referred to as Institutionalization Common Features because they:
- Ensure the process areas are effective, repeatable and lasting.
- Provide needed infrastructure support.
Common Feature Examples
- Commitment to perform: Establish and maintain an organizational policy for planning and performing the requirements management process.
- Ability to perform: Train the people performing or supporting the requirements management process as needed.
- Directing implementation: Place designated work products of the requirements management process under appropriate levels of configuration management.
- Verification: Review the activities, status, and results of the requirements management process with higher level management and resolve issues.
Summary
- Staged: Structured for implementation based on proven grouping and ordering of processes.
- The CMMI model should be applied using intelligence, common sense, and professional judgment.
⭐ Key Takeaways
The staged representation provides a predefined, sequential improvement path using five maturity levels that cannot be skipped, ensuring a disciplined foundation is established before progressing. Each maturity level contains specific process areas with goals that must be fully satisfied to achieve that rating, with lower-level goals being a prerequisite for higher levels. The model's structure includes process areas, specific and generic goals, specific and generic practices, and common features that ensure institutionalization. The progression from Level 1 to Level 5 moves from chaotic processes to quantitatively managed and optimizing processes, with the key difference between Level 3 (qualitatively predictable) and Level 4 (quantitatively predictable) being particularly important.
🧠 Quick Revision Questions
- What are the five maturity levels in the CMMI staged representation, and what is the key focus of each?
- Why can maturity levels not be skipped in the staged representation, and what risks does skipping introduce?
- What is the difference between a Specific Goal (SG) and a Generic Goal (GG), and what is the purpose of each?
- What are the four common features in the staged representation, and give an example of a generic practice for each?
- What is the key difference between a Level 3 (Defined) organization and a Level 4 (Quantitatively Managed) organization in terms of process predictability?
📘 Lecture 15 — CMMI Staged – Maturity Level 2
📖 Overview: This lecture examines CMMI Staged Representation, focusing on Maturity Level 2. It explains the evolutionary improvement path from ad-hoc Level 1 processes to managed Level 2 processes, detailing the seven process areas that establish fundamental project management discipline. Understanding this level is critical because it represents the biggest hurdle in process improvement—moving from chaotic individual practices to shared, repeatable project-level processes.
🗂️ Topics Covered
The lecture introduces the Staged Representation approach and the concept of maturity levels, then contrasts Level 1's ad-hoc processes with Level 2's disciplined management approach. It covers all seven Maturity Level 2 process areas in detail: Requirements Management, Project Planning, Project Monitoring and Control, Supplier Agreement Management, Measurement and Analysis, Process and Product Quality Assurance, and Configuration Management—including their specific goals, practices, generic practices, and common implementation pitfalls.
📝 Lecture Summary
Staged Representation
The staged representation uses 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. The biggest hurdle most organizations face is jumping from Level 1 to Level 2. Level 1 is characterized by ad hoc processes created by individuals, leading to redundant work, lack of sharing, opposing approaches, rework, delays, and frustration. The organization functions through heroics and suffers when people leave. Level 2 is characterized by individuals sharing lessons learned and best practices, devising preliminary processes that function at the project level and sometimes organization-wide.
💡 Why this matters: Level 1 organizations are fragile and dependent on individual heroics; Level 2 establishes the management discipline needed for predictable, repeatable project execution.
The Maturity Levels
Level 2 focuses on management issues that affect normal, day-to-day work routines and consists of seven process areas (PAs). Each PA has specific goals (specific to that PA) and generic goals applied to every PA at that maturity level. These generic goals lead to institutionalizing the process area—when an organization ensures consistent practice across the organization, the PA will continue to be applied appropriately even after those who created the procedures leave.
Generic Goal Level 2: Institutionalize a Managed Process consists of ten generic practices:
- GP 2.1 Establish an Organizational Policy
- GP 2.2 Plan the Process
- GP 2.3 Provide Resources
- GP 2.4 Assign Responsibility
- GP 2.5 Train People
- GP 2.6 Manage Configurations
- GP 2.7 Identify and Involve Relevant Stakeholders
- GP 2.8 Monitor and Control the Process
- GP 2.9 Objectively Evaluate Adherence
- GP 2.10 Review Status with Higher Level Management
PA 1 – Requirements Management
The purpose of Requirements Management (REQM) is to manage the requirements of the project's products and product components and to identify inconsistencies between those requirements and the project's plans and work products.
🔑 Definition — REQM: The process of understanding, obtaining commitment to, managing changes to, and maintaining traceability of requirements, while identifying inconsistencies between requirements and project work.
The specific goal (SG1) for REQM is Manage Requirements, with five specific practices:
- SP 1.1 Obtain an Understanding of Requirements
- SP 1.2 Obtain Commitment to Requirements
- SP 1.3 Manage Requirements Changes
- SP 1.4 Maintain Bidirectional Traceability of Requirements
- SP 1.5 Identify Inconsistencies between Project Work and Requirements
REQM at Level 2 focuses on managing already existing requirements—those elicited from the customer, documented, and ready to be worked. It exists at Level 2 because without setting scope, you cannot control how much work the project will need. The Requirements Development PA at Level 3 deals with eliciting and developing requirements, while REQM manages them. There are no generic practices that directly map to this PA. REQM includes understanding requirements for all parts of the system (not just software), obtaining commitment, managing changes, maintaining bidirectional traceability, and identifying inconsistencies. This PA forms the basis of project development and feeds into many other process areas.
PA 2 – Project Planning
The purpose of Project Planning (PP) is to establish and maintain plans that define project activities.
Three specific goals for PP:
- SG1 Establish Estimates
- SG2 Develop a Project Plan
- SG3 Obtain Commitment to the Plan
SG1 Specific Practices:
- SP 1.1 Estimate the Scope of the Project
- SP 1.2 Establish Estimates of Work Product and Task Attributes
- SP 1.3 Define Project Life Cycle
- SP 1.4 Determine Estimates of Effort and Cost
SG2 Specific Practices:
- SP 2.1 Establish the Budget and Schedule
- SP 2.2 Identify Project Risks
- SP 2.3 Plan for Data Management
- SP 2.4 Plan for Project Resources
- SP 2.5 Plan for Needed Knowledge and Skills
- SP 2.6 Plan Stakeholder Involvement
- SP 2.7 Establish the Project Plan
SG3 Specific Practices:
- SP 3.1 Review Plans That Affect the Project
- SP 3.2 Reconcile Work and Resource Levels
- SP 3.3 Obtain Plan Commitment
The generic practice that most closely matches PP is GP 2.2 Plan the Process. Other GPs that can trace guidance back to this PA include GP 2.3 (Provide Resources), GP 2.4 (Assign Responsibility), GP 2.5 (Train People), and GP 2.7 (Identify and Involve Relevant Stakeholders).
PA 3 – Project Monitoring and Control
The purpose of Project Monitoring and Control (PMC) is to provide an understanding of the project's progress so that appropriate corrective actions can be taken when the project's performance deviates significantly from the plan.
Two specific goals:
- SG1 Monitor Project against Plan
- SG2 Manage Corrective Action to Closure
SG1 Specific Practices:
- SP 1.1 Monitor Project Planning Parameters
- SP 1.2 Monitor Commitments
- SP 1.3 Monitor Project Risks
- SP 1.4 Monitor Data Management
- SP 1.5 Monitor Stakeholder Involvement
- SP 1.6 Conduct Progress Reviews
- SP 1.7 Conduct Milestone Reviews
SG2 Specific Practices:
- SP 2.1 Analyze Issues
- SP 2.2 Take Corrective Action
- SP 2.3 Manage Corrective Action
Key point: PMC is tied to the PP PA—without a credible project plan, PMC cannot be satisfied. Document reviews with management and any other reviews that may impact schedules, planning, staffing, or strategies. The generic practice that most closely matches this PA is GP 2.8 Monitor and Control the Process. Other related GPs are GP 2.7 (Identify and Involve Relevant Stakeholders) and GP 2.10 (Review Status with Higher Level Management). Reviews should be both periodic (routinely scheduled) and event-driven (when something unexpected happens or a milestone is reached). PMC includes monitoring project attributes, staff availability, stakeholder involvement, project risks, information handling, conducting reviews, bringing potential problems to light, analyzing issues, and taking corrective action.
PA 4 – Supplier Agreement Management
The purpose of Supplier Agreement Management (SAM) is to manage the acquisition of products from suppliers.
Two specific goals:
- SG1 Establish Supplier Agreements
- SG2 Satisfy Supplier Agreements
SG1 Specific Practices:
- SP 1.1 Determine Acquisition Type
- SP 1.2 Select Suppliers
- SP 1.3 Establish Supplier Agreements
SG2 Specific Practices:
- SP 2.1 Execute the Supplier Agreement
- SP 2.2 Monitor Selected Supplier Processes
- SP 2.3 Evaluate Selected Supplier Work Products
- SP 2.4 Accept the Acquired Product
- SP 2.5 Transition Products
SAM does not apply to projects where the supplier is integrated into the project team using the same processes and reporting to the same management. If the organization has no external suppliers, this PA may be non-applicable, though given the model's expanded nature, this is increasingly unlikely. The PA covers formal agreements for delivery, development, or installation of hardware, tools, COTS products, simulators, etc.—not just subcontracting. It includes guidance for releasing supplier-built products, evaluating project risks, and acceptance testing. Even though wording specifies "products and product components," practices also include services provided. This is the only PA that may be tailored out—it does not have to be implemented if it doesn't pertain to the organization. This PA does not map to any generic practice.
PA 5 – Measurement and Analysis
The purpose of Measurement and Analysis (M&A) is to develop and sustain a measurement capability that is used to support management information needs.
Two specific goals:
- SG1 Align Measurement and Analysis Activities
- SG2 Provide Measurement Results
SG1 Specific Practices:
- SP 1.1 Establish Measurement Objectives
- SP 1.2 Specify Measures
- SP 1.3 Specify Data Collection and Storage Procedures
- SP 1.4 Specify Analysis Procedures
SG2 Specific Practices:
- SP 2.1 Collect Measurement Data
- SP 2.2 Analyze Measurement Data
- SP 2.3 Store Data and Results
- SP 2.4 Communicate Results
M&A describes what to do when instituting a measurement process, not just which measurements to collect. It should be considered global because all processes should be measured. M&A was made a separate PA because high-maturity organizations identified measurement as key to success in process improvement. While instituting a measurement approach and repository is difficult, it is so necessary that it should be initiated early. Key reminders: tie measurements back to meaningful business goals (not just collecting because it's always been done); measure your measures—track the time, effort, and effectiveness of the measurement effort itself. The generic practice that most closely matches this PA is GP 2.8 Monitor and Control the Process—both M&A and PMC must be implemented to satisfy GP 2.8.
Basic Step-by-Step Approach to Measurement:
- Select the process to measure
- Select the measures
- Determine when to collect data
- Determine how to collect data
- Record and store the information
- Analyze data for consistency and accuracy
- Chart the results
- Review the chart
- Do something (corrective actions)
PA 6 – Process and Product Quality Assurance
The purpose of Process and Product Quality Assurance (PPQA) is to provide staff and management with objective insight into processes and associated work products.
Two specific goals:
- SG1 Objectively Evaluate Processes and Work Products
- SG2 Provide Objective Insight
SG1 Specific Practices:
- SP 1.1 Objectively Evaluate Processes
- SP 1.2 Objectively Evaluate Work Products and Services
SG2 Specific Practices:
- SP 2.1 Communicate and Ensure Resolution of Noncompliance Issues
- SP 2.2 Establish Records
Important: Someone needs to independently review QA activities and results—by another organization, outside the organization, or by companies specializing in IV&V or external audits. Some organizations use the SCAMPI appraisal itself as part of this external review. PPQA is the most often abused process area during appraisals—do not abuse or misuse it. If implementing PPQA as defined in CMMI is too much trouble, don't introduce CMMI. The generic practice that most closely matches this PA is GP 2.9 Objectively Evaluate Adherence. PPQA includes providing a strategy and procedures for objectively evaluating processes and products, identifying personnel to fulfill this role objectively, reporting quality issues and noncompliance, and producing verification reports.
PA 7 – Configuration Management
The purpose of Configuration Management (CM) is to establish and maintain the integrity of work products using configuration identification, configuration control, configuration status accounting, and configuration audits.
Three specific goals:
- SG1 Establish Baselines
- SG2 Track and Control Changes
- SG3 Establish Integrity
SG1 Specific Practices:
- SP 1.1 Identify Configuration Items
- SP 1.2 Establish a Configuration Management System
- SP 1.3 Create or Release Baselines
SG2 Specific Practices:
- SP 2.1 Track Change Requests
- SP 2.2 Control Configuration Items
SG3 Specific Practices:
- SP 3.1 Establish Configuration Management Records
- SP 3.2 Perform Configuration Audits
The organization needs to define when each type of baseline (formal or developmental) should be used. The generic practice that most closely matches this PA is GP 2.6 Manage Configurations—the term "configuration control" is used instead of "configuration management" when describing appropriate levels of configuration activities. CM includes defining configuration items, developing or implementing support tools and procedures, generating and maintaining baselines, tracking change requests and controlling changes, documenting results, and performing configuration audits.
⭐ Key Takeaways
Maturity Level 2 in CMMI Staged Representation transforms an organization from ad-hoc, heroics-dependent Level 1 to a managed state through seven process areas that establish fundamental project management discipline. The hardest jump in the entire CMMI model is Level 1 to Level 2, and success requires institutionalizing processes through ten generic practices applied across all PAs. Requirements Management (REQM) establishes scope control by managing existing requirements, while Project Planning (PP) and Project Monitoring and Control (PMC) form an inseparable pair—a credible plan is essential for effective monitoring and corrective action. Supplier Agreement Management (SAM) is unique as the only PA that can be tailored out if irrelevant, and Measurement and Analysis (M&A) emphasizes tying measurements to business goals rather than collecting data for its own sake. Process and Product Quality Assurance (PPQA) is the most frequently abused PA and requires truly objective evaluation, while Configuration Management (CM) ensures work product integrity through baselines, change control, and auditing.
🧠 Quick Revision Questions
- What is the fundamental difference between Maturity Level 1 and Maturity Level 2 processes?
- What are the seven process areas that make up Maturity Level 2, and which one is the only PA that can be tailored out?
- Why is Requirements Management (REQM) at Level 2 different from Requirements Development at Level 3?
- Why can't Project Monitoring and Control (PMC) be satisfied without first having a credible Project Plan (PP)?
- What is the basic nine-step approach to measurement, and why must you "measure your measures"?
📘 Lecture 16 — CMMI Staged – Maturity Level 3
📖 Overview: This lecture covers Maturity Level 3 of the CMMI staged representation, where an organization moves from project-level management to institutionalizing an organization-wide way of doing business. It details the attributes of a process, the distinction between managed and defined processes, and introduces the eleven process areas required at Level 3, including Requirements Development, Technical Solution, and Product Integration.
🗂️ Topics Covered
The lecture begins by explaining the fundamental shift from Level 2 to Level 3, where best practices from projects are aggregated into an Organizational Set of Standard Processes (OSSP) with a tailoring mechanism. It then defines the standard attributes of a process and distinguishes between a managed process and a defined process. The core of the lecture lists the eleven process areas for Level 3 and provides a detailed breakdown of three of them: Requirements Development (RD), Technical Solution (TS), and Product Integration (PI), including their specific goals, practices, and common pitfalls.
📝 Lecture Summary
Maturity Level
Maturity Level 3 differs from Level 2 because an organizational way of doing business has been developed. The best practices and lessons learned from projects have bubbled up to the organizational level to create an organizational identity. There are common, shared approaches for performing daily tasks on each project. For example, estimating the size of a project may be done using the Delphi Technique, a standard metric may have been institutionalized (such as using function points instead of lines of code), and a standard tool may be in use to calculate the size.
This organizational way of doing business is documented in the Organization’s Set of Standard Processes (OSSP). However, should a project need to tailor this OSSP to fit its needs more adequately, then that tailoring request is brought to a decision-making body (usually the Engineering Process Group [EPG] ), and if appropriate, the request is granted. An example may be a legacy system that calculates size by lines of code instead of by function point. Rather than reengineer the millions of lines of code, the project is simply allowed to continue calculating size by lines of code. To perform at Level 3, an organization must have satisfied all of the goals for all of the process areas (PAs) in both Level 2 and Level 3. Sometimes exceptions may be made, but caution should be exercised. Entire process areas are generally not allowed to be tailored out of consideration. Practices may be tailored out if replaced by sufficient alternative practices.
💡 Why this matters: The shift to Level 3 represents a cultural change where project-level successes become organization-wide standards, enabling more predictable and repeatable performance across the entire enterprise.
Attributes of a Process suggested by CMMI
A process must have clearly defined attributes:
- Purpose—The purpose of the process.
- Inputs—Work products, plans, approval memoranda (usually nouns).
- Entry criteria—What must be triggered before this process can start? (Usually the exit criteria of the previous step or process, stated as a verb.)
- Activities—Tasks that must be performed, often broken down into detailed procedures.
- Roles—Who does what? (Usually by position.)
- Measures—What measures does this process produce?
- Verification steps—What reviews are performed to determine that this process is followed and is producing the correct results? (Usually management and quality assurance reviews.)
- Outputs—Work products, plans, approved products (can be the completed inputs).
- Exit criteria—How do we know when it is time to stop this process? (Usually expressed in verbs, and usually becomes the entry criteria for the next process step or next process.)
Managed Process
Another distinction is made concerning processes. A managed process is a process that tackles project management efforts, is planned and executed according to a policy, is monitored, and reviewed to ensure adherence to its process description. This is the type of process expected at Maturity Level 2.
Defined Process
A defined process builds upon a managed process by creating an organizational process that is then tailored to fit the needs of a particular project and involves gathering information related to improvement efforts undertaken by the organization in order to improve both the organization-level process and the project-level process.
Process Areas for Maturity Level 3
The process areas for Maturity Level 3 are:
- Requirements Development
- Technical Solution
- Product Integration
- Verification
- Validation
- Organizational Process Focus
- Organizational Process Definition (with IPPD)
- Organizational Training
- Integrated Project Management (with IPPD)
- Risk Management
- Decision Analysis and Resolution
To satisfy the goals for Level 3, the goals for Level 2 must be satisfied as well. This mandate holds true for both the specific goals and the generic goals. There are two generic goals for levels 2 and 3:
- GG2 Institutionalize a Managed Process
- GG3 Institutionalize a Defined Process
GG2 Institutionalize a Managed Process – Generic Practices
The generic practices for GG2 are:
- GP 2.1 Establish an Organizational Policy
- GP 2.2 Plan the Process
- GP 2.3 Provide Resources
- GP 2.4 Assign Responsibility
- GP 2.5 Train People
- GP 2.6 Manage Configurations
- GP 2.7 Identify and Involve Relevant Stakeholders
- GP 2.8 Monitor and Control the Process
- GP 2.9 Objectively Evaluate Adherence
- GP 2.10 Review Status with Higher Level Management
GG3 Institutionalize a Defined Process – Generic Practices
The generic practices for GG3 are:
- GP 3.1 Establish a Defined Process
- GP 3.2 Collect Improvement Information
PA 1 – Requirements Development (RD)
The purpose of Requirements Development (RD) is to produce and analyze customer, product, and product component requirements. This process area is where requirements are created and documented, while Requirements Management at Level 2 is where changes are administered. RD gathers requirements and then refines them—stating them more clearly, determining redundancy or inconsistency, and breaking them down into more detailed and traceable requirements. Even maintenance shops have development since there are always new requirements or changes to existing ones. This process area introduces the Concept of Operations or, using the CMMI term, operations concept, which is a high-level statement of desired functionality and a preliminary plan to justify the project.
Specific goals for this process area are:
- SG1 Develop Customer Requirements
- SP 1.1 Elicit Needs
- SP 1.2 Develop the Customer Requirements
- SG2 Develop Product Requirements
- SP 2.1 Establish Product and Product Component Requirements
- SP 2.2 Allocate Product Component Requirements
- SP 2.3 Identify Interface Requirements
- SG3 Analyze and Validate Requirements
- SP 3.1 Establish Operational Concepts and Scenarios
- SP 3.2 Establish a Definition of Required Functionality
- SP 3.3 Analyze Requirements
- SP 3.4 Analyze Requirements to Achieve Balance
- SP 3.5 Validate Requirements
Things People Forget:
- Maintenance shops also do development.
- Even if you get your requirements directly from the customer, some refinement and analysis is always necessary.
- Developing and analyzing requirements never stops until the entire application is delivered or dead and buried.
- There are no generic practices that directly map to this process area.
PA 2 – Technical Solution (TS)
The purpose of Technical Solution (TS) is to design, develop, and implement solutions to requirements. In this process area, when the model refers to processes, it generally means design processes, not process improvement–type processes. Peer reviews are mentioned in this process area. A key thing people forget is that alternative solutions should be investigated.
Specific goals for Technical Solution are:
- SG1 Select Product Component Solutions
- SP 1.1 Develop Alternative Solutions and Selection Criteria
- SP 1.2 Select Product Component Solutions
- SG2 Develop the Design
- SP 2.1 Design the Product or Product Component
- SP 2.2 Establish a Technical Data Package
- SP 2.3 Design Interfaces Using Criteria
- SP 2.4 Perform Make, Buy, or Reuse Analyses
- SG3 Implement the Product Design
- SP 3.1 Implement the Design
- SP 3.2 Develop Product Support Documentation
PA 3 – Product Integration
The purpose of Product Integration (PI) is to assemble the product from the product components, ensure that the product functions properly, and deliver the product. This is where the product comes together and you get to see the results of your work. It is also where you deliver the product, which means you get paid. This process area expects the project to demonstrate each step to the user. This process area is not release management.
Specific goals for this process area are:
- SG1 Prepare for product integration
- SP 1.1 Determine Integration Sequence
- SP 1.2 Establish the Product Integration Environment
- SP 1.3 Establish Product Integration Procedures and Criteria
- SG2 Ensure Interface Compatibility
- SP 2.1 Review Interface Descriptions for Completeness
- SP 2.2 Manage Interfaces
- SG3 Assemble Product Components and Deliver the Product
- SP 3.1 Confirm Readiness of Product Components for Integration
- SP 3.2 Assemble Product Components
- SP 3.3 Evaluate Assembled Product Components
- SP 3.4 Package and Deliver the Product or Product Component
Things People Forget:
- The nightly build does not satisfy all of the Product Integration process area practices.
- You must analyze the problems that occur and see if any of the integrated components conflict with remaining components.
- The emphasis is on being proactive and identifying problems early, rather than being reactive to problems that pop up during the nightly run.
- There are no generic practices that directly map to this process area.
🔑 Definition — Delphi Technique: A technique where subject matter experts discuss best-case and worst-case estimates to arrive at a project estimate.
🔑 Definition — OSSP (Organization’s Set of Standard Processes): The documented set of organizational standard processes that defines the organization-wide way of doing business.
🔑 Definition — EPG (Engineering Process Group): The decision-making body that reviews and approves tailoring requests to the OSSP.
🔑 Definition — Managed Process: A process that tackles project management efforts, is planned and executed according to a policy, is monitored, and reviewed to ensure adherence to its process description (expected at Level 2).
🔑 Definition — Defined Process: A process that builds upon a managed process by creating an organizational process that is tailored to fit the needs of a particular project (expected at Level 3).
🔑 Definition — Concept of Operations (Operations Concept): A high-level statement of the desired functionality, and a preliminary plan and schedule for development, to justify initiating a new project.
⭐ Key Takeaways
At Maturity Level 3, an organization establishes a standard way of doing business documented in the OSSP, which projects can tailor with approval from the EPG. The key distinction is between a managed process (Level 2, project-level planning and monitoring) and a defined process (Level 3, organizational standards that are tailored). The three process areas detailed—Requirements Development, Technical Solution, and Product Integration—cover creating and refining requirements, designing technical solutions with alternative analysis, and assembling and delivering the final product. A critical exam point is that even maintenance organizations perform development activities and must refine requirements, and that the nightly build does not satisfy the proactive analysis required by Product Integration.
🧠 Quick Revision Questions
- What is the fundamental difference between a managed process (Level 2) and a defined process (Level 3)?
- What is the role of the Engineering Process Group (EPG) in the context of the OSSP at Maturity Level 3?
- What is the primary purpose of Requirements Development (RD), and how does it differ from Requirements Management?
- In the Technical Solution (TS) process area, what is a common mistake organizations make regarding solution selection?
- Why does a "nightly build" alone not satisfy all the practices of the Product Integration (PI) process area?