Microsoft has built in Azure Devops support to be able to work with different standards such as in general as well as Scrum and CMMI.
In our analysis, we have chosen CMMI as Scrum is included in a separate analysis (see Scrum and Prime Arch) and CMMI is a good complement.
About CMMI:
One disadvantage is that it is difficult to find concrete references to how CMMI views implementation. The material available is from Microsoft and Azure Devops, which means that we can start from their interpretation of the CMMI standard.
Azure Devop's set of Product Backlog management objects according to CMMI looks like this:
As shown above, three objects are used for "backlog": Epic, Feature and Requirement. Definitions of these are missing, but the documentation is practically oriented with a focus on how to work in Azure Devops.
Tasks are concrete tasks that must be performed, which is not part of the deliverable structure.
We include the following objects in the further analysis:
- Epic
- Feature
- Requirement
To proceed further in the analysis, a comparison of other established standards such as Atlassian and Scrum is required. The result of the overall analysis is described in the article "Implementation hierarchy in different standards".