KodeKloud Notes

In this lesson, we dive into the Capability Maturity Model Integration (CMMI) process template available in Azure DevOps. CMMI delivers a structured framework for process improvement, rigorous audit trails, and decision tracking—ideal for teams managing complex requirements, change requests, and risk mitigation.

When to Choose CMMI

Note

CMMI is designed for organizations that require formal governance, regulatory compliance, and comprehensive traceability across all deliverables.

Formalize process improvement and governance
Maintain an immutable audit trail of key decisions
Track detailed requirements, change requests, and risks
Support enterprise-level change management and compliance

Azure DevOps CMMI Work Item States

CMMI enforces a four-stage lifecycle for every work item:

Proposal
New work items or change requests are defined and evaluated.
Active
Items under detailed development, analysis, or review.
Resolved
Completed work is marked as addressed, awaiting verification.
Closed
Final approval, sign-off, and archival.

The image illustrates a "Flow of Work" diagram for CMMI, showing stages labeled as Proposal, Active, Resolved, and Closed, connected to a central "States" icon.

CMMI Work Item Types

The CMMI template in Azure DevOps includes these core work item types, ensuring end-to-end traceability:

Work Item Type	Purpose	Example
EPIC	High-level objective spanning multiple releases	Migrate legacy reports to Power BI
Feature	Discrete deliverable within an EPIC	Implement OAuth2 authentication
Requirement	Specific criteria derived from a Feature	Support multi-factor login
Task	Atomic unit of work linked to a Requirement	Write API integration tests
Bug	Code or configuration defects	Fix null-pointer exception in login
Change Request	Proposed change to scope, schedule, or cost	Adjust sprint backlog for new UI
Issue	Immediate impediment or blocker	Resolve build pipeline failures
Review	Formal evaluation and approval record	UX design review checklist
Risk	Potential future problem requiring mitigation plans	Single point of failure in database

Testing Structure in CMMI

A modular testing hierarchy promotes reusability and comprehensive coverage:

Test Plan
Overall testing strategy, scope, and goals.
Test Suite
Logical grouping of related test cases.
Test Case
Detailed steps verifying a specific feature or requirement.
Shared Steps
Reusable sequences (e.g., login, API call) across multiple test cases.
Shared Parameters
Data sets enabling data-driven testing scenarios.

The image is a flowchart illustrating a testing process, starting with "Test Plan" and progressing through "Test Suite," "Test Case," and ending with "Shared Steps" and "Shared Parameters."

Feedback Management Workflow

CMMI embeds structured feedback loops to engage stakeholders early and often:

Feedback Request
Invite stakeholders to review features, designs, or deliverables.
Feedback Response
Gather comments, suggestions, or approval decisions.

The image shows a flowchart with two connected boxes labeled "Feedback Request" and "Feedback Response," illustrating a feedback process.

Code Review Workflow

Ensuring code quality and compliance through peer reviews:

Code Review Request
Developer submits code changes for evaluation.
Code Review Response
Reviewers provide feedback, approval, or additional change requests.

The image shows a flowchart with two connected boxes labeled "Code Review" and "Code Review Response," indicating a process or sequence.

Next Steps

With the CMMI process template established, our next topic will cover activity traceability, enabling you to link requirements, tasks, test cases, and code changes for full lifecycle visibility.

References

Watch Video

Watch video content