KodeKloud Notes

In this article, we explore the CMMI process model and its structure for formal project management within Azure DevOps. The CMMI framework is ideal if your team requires a comprehensive process improvement methodology that provides a detailed audit trail and clear records of decisions. It is particularly effective for tracking requirements, managing change requests, and mitigating risks, making it an excellent option for teams handling frequent changes.

Work Items and Process States

The CMMI model uses various work item types to plan, track, and improve projects continuously. Work items typically progress through the following states:

– Proposal: New tasks or changes are initiated.
– Active: Work is in progress.
– Resolved: A developer marks the task as complete.
– Closed: The change is approved and finalized.

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

The CMMI process template supports several work item types (WITs) that streamline the management of work, tests, feedback, and code reviews. When setting up a project with the CMMI process, work item types such as requirements, change requests, tasks, and bugs are automatically created.

Hierarchical Structure

The hierarchy in the CMMI model begins with EPICs, which represent large-scale objectives that span multiple sprints or releases. These EPICs break down into features, representing distinct serviceable components. From features, requirements are defined to establish necessary criteria, and finally, tasks emerge as actionable items for implementation.

The image illustrates a "Flow of Work" in CMMI, showing a progression from "Epics" to "Feature" to "Requirements" with corresponding icons.

In addition, bugs and tasks—primarily related to code defects—are managed in tandem, with all tasks associated with a bug being traceable to that issue. Moreover, change requests handle project adjustments, issues address immediate impediments, reviews facilitate evaluations, and risks highlight potential future problems. This organized structure enhances project management and quality assurance within the CMMI framework.

The image illustrates a "Flow of Work" for CMMI, featuring elements like Bugs, Tasks, Change Request, Risk, Review, and Issues, each represented by icons.

Testing Process in CMMI

Testing is meticulously structured within the CMMI template. A test plan outlines the overall testing strategy and divides into test suites, which are collections of related test cases. Each test case verifies specific functions or pieces of code.

The image is a flowchart illustrating a testing process, starting with a "Test Plan" leading to "Test Suite," then "Test Case," and branching into "Shared Steps" and "Shared Parameters."

Note

Shared steps are sequences of actions applicable across multiple tests, promoting reusability and efficiency. Similarly, shared parameters facilitate data-driven testing to ensure comprehensive validation throughout the development lifecycle.

Feedback Mechanism

Feedback is a cornerstone of the CMMI process. A feedback request is used to invite stakeholders to review specific features or project components. Stakeholders then submit their responses, providing valuable insights, suggestions, or approvals. This iterative feedback loop is essential for continuous improvement and alignment with stakeholder expectations.

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

Formal Code Review

The CMMI model integrates a formal code review process. When a developer initiates a code review request, peers are invited to assess the functionality, quality, and integration of the new or modified code. The process culminates in a code review response that may include feedback, approvals, or recommendations for further modifications.

Note

A structured code review process ensures the maintenance of high code quality and adherence to project standards while also encouraging collaborative development practices.

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

Activity Traceability

Finally, activity traceability is crucial within the CMMI framework. It ensures that every project operation is logged, providing detailed historical data that is essential for audits, continuous improvement, and effective project management.

By leveraging the structured approach of the CMMI process, teams can achieve greater project visibility, improved quality assurance, and more efficient change management—all key factors in the successful delivery of projects within Azure DevOps.

Watch Video

Watch video content