Achieving SEI CMM Level 5 from Level 4: What Extra Practice Is Required for Defects?
An organization assessed at SEI CMM Level 4 must already have strong quantitative management and managed improvement capabilities. In many exam-style mappings, Level 5’s “additional” emphasis is systematic defect prevention driven by root-cause analysis and process improvement beyond merely managing how processes/technologies change.
Given the prompt:
- The organization already practices (i.e., as Level 4 capability) Process Change Management and Technology Change Management.
- To achieve Level 5, it also needs to practice defect prevention (more than defect detection/isolation/propagation).
This corresponds to selecting (ii) Defect prevention.
Key idea: Level 5 focuses on preventing recurring problems by using data and causal analysis to eliminate root causes, not just improving detection or containment. This shifts the organization from “manage defects” to “prevent defects at their source.”
Exam Strategy
If the question already grants Process Change Management and Technology Change Management, Level 5’s distinguishing “defect-focused” option is the one about prevention—i.e., fixing causes so defects don’t re-occur.
To reason through the options, interpret each “defect-*” capability:
- keyword: locating defects during review/test.
- keyword: containment via compartmentalization/segmentation.
- keyword: tracing upstream/downstream effects.
- keyword: improving processes so defects do not occur in the first place.
At Level 5, the organization’s improvement is expected to be proactive: it uses measured causes and patterns to prevent recurrence. That aligns with defect prevention (not only detection/isolation/propagation).
Therefore, the correct choice is: (ii) Defect prevention.
Selecting the Correct Level 5 Practice from the Options
- 1Step 1
The prompt states the organization already practices Process Change Management and Technology Change Management—so those are not the “extra” Level 5 requirement.
- 2Step 2
Level 5 emphasizes preventing problems by using causal analysis and continuous improvement that targets root causes.
- 3Step 3
Defect detection/isolation/propagation are primarily reactive/containment activities; defect prevention is the proactive, root-cause activity.
- 4Step 4
Select (ii) Defect prevention.
From Level 4 to Level 5 Defect Management
Managed improvement via change
Level 4Uses managed process/technology change and quantitative understanding."
Causal, prevention-oriented improvement
Transition to Level 5Uses data to find root causes and designs changes to prevent recurrence."
Defect prevention becomes central
Level 5Prevention-focused practices reduce the introduction of defects, not just their discovery or containment."
How Each Defect Option Aligns with a Prevention-Oriented Level 5 Goal
Higher score indicates closer alignment to proactive prevention rather than reactive containment.
Quick FAQ on the Options
CMMI Maturity Levels Overview (Level 4 vs Level 5) — Process Improvement Concepts
Level 5 Defect-Focus Flashcards
Knowledge Check
Given that Process Change Management and Technology Change Management are already practiced, which additional practice is needed to achieve SEI CMM Level 5?
Explore Related Topics
8051 Port 3 Alternate Functions: Identifying the Incorrect Option
Port 3 of the 8051 provides eight alternate pin functions (RXD/TXD, INT0/INT1, T0/T1, WR/RD), so the only option that does not belong to its alternate functions is internal interrupts.
- P3.0 = RXD and P3.1 = TXD for serial communication.
- P3.2 = INT0 and P3.3 = INT1 for external interrupts.
- P3.4 = T0 and P3.5 = T1 as timer external inputs.
- P3.6 = WR and P3.7 = RD for external memory control.
- Internal interrupts arise from on‑chip peripherals, not from any Port 3 pin.
Group Discussion Evaluation: Why the Correct Answer Is Communication and Teamwork
Group discussions are used in recruitment and education to assess participants' communication and teamwork rather than writing, coding, or memory.
- Evaluators watch for clear speaking, active listening, relevance, collaborative engagement, and respectful conflict handling.
- Leadership, initiative, and problem‑solving are secondary but still observed.
- Written ability, technical coding, and pure recall are not primary targets in GDs.
- Success depends on oral interaction; the core metric can be expressed as .
Data Preprocessing Steps: Identifying What’s NOT Part of Preprocessing