Our CMMI Journey: Where Adoption Gets Real
Most software teams have some process on paper. The harder question is whether it is how the work actually gets done. Since August, we've been working towards CMMI-DEV Maturity Level 3, and the most useful lesson so far is about adoption, not documentation.
What CMMI-DEV is, in a minute
CMMI-DEV is a globally recognised model from ISACA for how teams build software. It groups good practice into Practice Areas, such as:
Maturity Level 3 means standard processes are defined across the organisation and tailored to each project. The model describes what good looks like; how to apply it is up to each organisation.
Documented is not the same as used
In many teams, process documents exist but sit beside the work instead of inside it. Steps get decided on the spot, and the record of what happened lives in people's heads, inboxes and chat threads. That works until someone is away, a project changes hands, or a client asks how a decision was made.
Documented is what you wrote. Used is what you do.
Recent research points the same way:
This matches what we see: knowledge that lives with people slows teams down, and processes stick when leaders visibly back them.
What we built
We built our process as a Process Asset Library (PAL), one place that holds four things:
Policies
What we commit to.
SOPs
How each activity is done, step by step.
Templates
The standard records every project fills in.
Process Tailoring Guidelines
How processes are tailored for different types of projects.
Every project runs through the same stages. Each stage uses the PAL and leaves records we can check:
How we make it stick
Writing the process is only half the work. Adoption comes from three habits:
Management expects it, and checks it
Trackers, project reviews and a monthly review show whether the process is being followed.
The whole team is trained
Regular training makes the process something people know, not something they look up.
The process keeps improving
In the monthly review we adjust it based on what the team actually experiences.
What we're seeing so far
A few of many changesWe're still on the journey, and the changes are already visible. These are a few of the many we're seeing:
Changes arrived through several channels and were handled by different people.
Every change comes in as a helpdesk ticket, is logged as a change request on the project, and is implemented from there.
Steps had no defined timelines.
Every process and step has a set number of business days to be completed, so closing a project no longer waits indefinitely.
Client conversations stayed with the person who had them.
All client interactions, by anyone on the team, are recorded in one central place, so everyone has the context.
- ✓Smoother handovers. When someone moves on, credentials, responsibilities and project records are documented and held by the company, so the handover is complete.
- ✓Faster onboarding. As documentation fills in, a new team member's ramp-up is moving from weeks towards days.
- ✓Lessons that become rules. Testing on client systems happens outside their working hours, backups are taken regularly, and migrations follow SOPs.
- ✓A language larger clients speak. Enterprise projects often ask for CMMI or ISO credentials, and a defined process gives us something concrete to point to.
What it means for everyone involved
Clients
Clearer scope and change handling, regular status updates, a defined support period and a documented handover.
Delivery
Less dependence on individuals, faster onboarding and fewer repeated mistakes through lessons learned.
Sales
Consistent qualification, a clear process to point to in proposals, and a credible quality signal for larger clients.
Management
A record of what happened on each project, and early warning of gaps from the monthly reviews.
A quick check: is your process really used?
- 1Are the records for your last project in a shared system, not in someone's inbox?
- 2Could a new joiner pick up a live project from the documents alone?
- 3When scope or team changes, does it go through a defined step?
- 4Does someone check on a regular schedule that the process is followed?
- 5Does the process change when the team finds a better way?
We'll keep sharing what we learn on the way to Maturity Level 3. If you're thinking about CMMI for your own team, we're happy to talk through how we've been doing it.
- Google Cloud DORA (2023). Accelerate State of DevOps Report 2023.
- Stack Overflow (2024). 2024 Developer Survey.
- Prosci (2023). Best Practices in Change Management, 12th Edition.
Want to implement CMMI as well?
Discuss with us and we'll walk you through how we have been doing it.
Get In TouchOur CMMI Journey: Where Adoption Gets Real
Most software teams have some process on paper. The harder question is whether it is how the work actually gets done. Since August, we've been working towards CMMI-DEV Maturity Level 3, and the most useful lesson so far is about adoption, not documentation.
What CMMI-DEV is, in a minute
CMMI-DEV is a globally recognised model from ISACA for how teams build software. It groups good practice into Practice Areas, such as:
Maturity Level 3 means standard processes are defined across the organisation and tailored to each project. The model describes what good looks like; how to apply it is up to each organisation.
Documented is not the same as used
In many teams, process documents exist but sit beside the work instead of inside it. Steps get decided on the spot, and the record of what happened lives in people's heads, inboxes and chat threads. That works until someone is away, a project changes hands, or a client asks how a decision was made.
Documented is what you wrote. Used is what you do.
Recent research points the same way:
This matches what we see: knowledge that lives with people slows teams down, and processes stick when leaders visibly back them.
What we built
We built our process as a Process Asset Library (PAL), one place that holds four things:
Policies
What we commit to.
SOPs
How each activity is done, step by step.
Templates
The standard records every project fills in.
Process Tailoring Guidelines
How processes are tailored for different types of projects.
Every project runs through the same stages. Each stage uses the PAL and leaves records we can check:
How we make it stick
Writing the process is only half the work. Adoption comes from three habits:
Management expects it, and checks it
Trackers, project reviews and a monthly review show whether the process is being followed.
The whole team is trained
Regular training makes the process something people know, not something they look up.
The process keeps improving
In the monthly review we adjust it based on what the team actually experiences.
What we're seeing so far
A few of many changesWe're still on the journey, and the changes are already visible. These are a few of the many we're seeing:
Changes arrived through several channels and were handled by different people.
Every change comes in as a helpdesk ticket, is logged as a change request on the project, and is implemented from there.
Steps had no defined timelines.
Every process and step has a set number of business days to be completed, so closing a project no longer waits indefinitely.
Client conversations stayed with the person who had them.
All client interactions, by anyone on the team, are recorded in one central place, so everyone has the context.
- ✓Smoother handovers. When someone moves on, credentials, responsibilities and project records are documented and held by the company, so the handover is complete.
- ✓Faster onboarding. As documentation fills in, a new team member's ramp-up is moving from weeks towards days.
- ✓Lessons that become rules. Testing on client systems happens outside their working hours, backups are taken regularly, and migrations follow SOPs.
- ✓A language larger clients speak. Enterprise projects often ask for CMMI or ISO credentials, and a defined process gives us something concrete to point to.
What it means for everyone involved
Clients
Clearer scope and change handling, regular status updates, a defined support period and a documented handover.
Delivery
Less dependence on individuals, faster onboarding and fewer repeated mistakes through lessons learned.
Sales
Consistent qualification, a clear process to point to in proposals, and a credible quality signal for larger clients.
Management
A record of what happened on each project, and early warning of gaps from the monthly reviews.
A quick check: is your process really used?
- 1Are the records for your last project in a shared system, not in someone's inbox?
- 2Could a new joiner pick up a live project from the documents alone?
- 3When scope or team changes, does it go through a defined step?
- 4Does someone check on a regular schedule that the process is followed?
- 5Does the process change when the team finds a better way?
We'll keep sharing what we learn on the way to Maturity Level 3. If you're thinking about CMMI for your own team, we're happy to talk through how we've been doing it.
- Google Cloud DORA (2023). Accelerate State of DevOps Report 2023.
- Stack Overflow (2024). 2024 Developer Survey.
- Prosci (2023). Best Practices in Change Management, 12th Edition.
Want to implement CMMI as well?
Discuss with us and we'll walk you through how we have been doing it.
Get In Touch