The original maturity model is the Capability Maturity Model invented at Carnegie Mellon University (CMU). It is a bit heavy to fully utilize, so simplified, more lightweight versions of it are preferable. One such version is the Four Quadrant Model put forward by Brian Dawson (https://techbeacon.com/devops/how-map-your-devops-journey). It is derived from real-world DevOps transformations and offers a flexible way to assess maturity.
In the Four Quadrant Model, the values on the x axis consist of the different phases in the cycle of software development. You can recognize the Software Development Life Cycle (SDLC) in this:
- Define
- Plan
- Code
- Build
- Integrate
- Test
- Release
- Deploy
- Operate
You see there is quite some overlap with the DevOps lifecycle phases that are proposed by GitLab.
The cycle is divided into two halves: Agile Upstream (which includes a definition, planning, coding, and building) and Agile Downstream (which includes integration, testing, release, implementation, and methods such as continuous deployment and continuous delivery).
On the y axis, there is the level of adoption of Agile and DevOps practices in an organization. At the lower end, there is the team level, which moves on to the workgroup level, and finally the enterprise level. In the original CMMI model, there are usually different levels of maturity. The following figure illustrates the 4 Quadrant model:
Agile Upstream means that in a software life cycle, the development side of the product is done with Agile methodologies. Agile Downstream is all about the deployment and operational side of the SDLC.
Each team must strive to implement the Four Quadrant Model because it enables them to innovate faster, increase productivity, respond to market changes, gain a competitive advantage, and increase employee satisfaction and retention.
Another way of measuring maturity is to look at competencies. How strong are you in certain aspects, for example?