Skip to main content
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

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:
  1. Proposal
    New work items or change requests are defined and evaluated.
  2. Active
    Items under detailed development, analysis, or review.
  3. Resolved
    Completed work is marked as addressed, awaiting verification.
  4. 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 TypePurposeExample
EPICHigh-level objective spanning multiple releasesMigrate legacy reports to Power BI
FeatureDiscrete deliverable within an EPICImplement OAuth2 authentication
RequirementSpecific criteria derived from a FeatureSupport multi-factor login
TaskAtomic unit of work linked to a RequirementWrite API integration tests
BugCode or configuration defectsFix null-pointer exception in login
Change RequestProposed change to scope, schedule, or costAdjust sprint backlog for new UI
IssueImmediate impediment or blockerResolve build pipeline failures
ReviewFormal evaluation and approval recordUX design review checklist
RiskPotential future problem requiring mitigation plansSingle 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:
  1. Feedback Request
    Invite stakeholders to review features, designs, or deliverables.
  2. 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:
  1. Code Review Request
    Developer submits code changes for evaluation.
  2. 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