Measuring agile maturity: A simple 90-day plan
Measuring agile maturity should not end in an abstract agility score. Agile maturity is meant to make visible where concrete problems exist so that these obstacles can be systematically removed.
The most important rule up front: only measure agile maturity if it is meant to lead to concrete improvements. Measuring maturity without follow-up action creates reporting effort and a bad atmosphere due to a lack of progress.
Measuring agile maturity: A brief summary
If you have little time, use this sequence:
- Clarify the goal: Why do you want to increase your agile maturity? Faster delivery, better quality, closer customer proximity, greater team accountability?
- Choose the model: Use dimensions optimized for the goal (2 to 4 maturity dimensions are enough) instead of an overloaded framework.
- Measure the baseline: Combine team feedback, delivery metrics, and observations.
- Reflect on the results: Discuss the data in team retrospectives, not just in management reporting.
- Derive measures: Prioritize a maximum of 1 to 2 improvements per team.
- Re-measure: Measure again after 6 to 12 weeks and compare trends within the same team.
Good maturity measurement answers three questions: Where do we stand? What is slowing us down? Which change do we test next?
What is agile maturity?
Agile maturity describes how effectively agile principles are lived in everyday work. It is less about the existence of Scrum events or Jira boards and more about observable behavior:
- Teams deliver usable results regularly.
- Feedback from customers and stakeholders influences priorities.
- Retrospectives lead to visible improvements.
- Decisions are made where the relevant information is located.
- Leadership creates clarity, focus, and psychological safety.
- Teams use metrics without turning them into a control system.
High agile maturity is evident when an organization learns faster than its problems grow.
Which dimensions should you measure?
For practice, an approach tailored to the goal is usually enough: choose from these six dimensions. They are concrete enough for teams and broad enough for organizations:
| Dimension | Guiding question | Typical indicators |
|---|---|---|
| Customer orientation | Are we learning regularly from the market? | Feedback loops, usage data, stakeholder satisfaction |
| Delivery capability | Are we delivering value reliably? | Lead time, delivery frequency, predictability |
| Quality | Do results remain stable? | Defects, rework, technical debt |
| Team autonomy | Can teams make effective decisions? | Dependencies, role clarity, decision paths |
| Learning culture | Are problems being improved openly? | Retro effectiveness, willingness to experiment, error culture |
| Leadership & alignment | Is there orientation without micromanagement? | Clarity of goals, prioritization, cross-functional alignment |
Important: do not compare teams against each other. A team with a legacy system, high dependencies, and many support requests has different conditions than a new product team. Compare trends within the same team.
The 5 stages of agile maturity
A simple stage model helps with classification. Use it as a basis for discussion, not as certification.
- Reactive: Work is highly ad hoc. Retrospectives take place irregularly or remain without consequence.
- Repeatable: Agile events exist, but quality and reliability vary.
- Established: Team processes are stable. Obstacles are made visible and improved regularly.
- Data-driven proactive: Teams combine feedback, metrics, and observation to make proactive decisions before problems escalate.
- Learning: Continuous improvement is part of the culture. Learning happens across teams and is actively enabled by leadership.
The most important boundary lies between stage 2 and 3: there, for the first time, “we do agile rituals” becomes “we measurably improve our collaboration and delivery with them”.
Which metrics for agile maturity make sense?
A reliable picture emerges from several perspectives. No single metric shows agile maturity reliably.
- Delivery: Lead time, delivery frequency, predictability, work in progress.
- Quality: Defect rate, rework, stability, technical debt.
- Team: psychological safety, focus, role clarity, energy levels, collaboration.
- Customer value: feedback cycle, usage data, satisfaction, outcome metrics.
- Improvement: implemented retro actions, learning experiments, removed blockers.
Avoid vanity metrics like “number of Scrum events”, “velocity in team comparison” or “agility in percent”. They seem objective, but often lead to misdirection.
30-60-90-day plan for measurement
Days 1 to 30: establish a baseline
Start small. Choose 3 to 5 teams, a clear goal, and a few dimensions. Conduct a short health check, supplement existing delivery data, and collect qualitative observations from retrospectives or interviews.
Good baseline questions are:
- Where are we currently losing the most time?
- Which decisions are taking too long?
- Where is customer or stakeholder feedback missing?
- Which retro actions were actually implemented?
- Which dependencies regularly slow us down?
Days 31 to 60: translate results into actions
The evaluation belongs in the teams. Show trends, outliers, and tensions, but avoid rankings. For each team, only 1 to 2 actions should emerge, for example:
- Test a WIP limit to reduce parallel work.
- Refine the Definition of Done to reduce rework.
- Build stakeholder review into the sprint earlier.
- Define a decision rule for recurring dependencies.
- Assign retro actions a clear responsible person.
Days 61 to 90: remeasure and learn
After 6 to 12 weeks, you measure again. What matters is not whether every value increases, but whether the team tests hypotheses and makes better decisions.
A good review question is: “Which change demonstrably helped, which did not, and what do we learn from it?”
Agile maturity models compared
There are many models. For selection, it is less important which model is the best known, and more whether it improves decisions.
| Model | Strengths | Caution |
|---|---|---|
| Great Place to Work Agility Module | Combines culture and processes | Often more of an organizational diagnosis than a team tool |
| New Work Transformation Model | Helpful for autonomy, mindset, and leadership | Requires good facilitation and contextual knowledge |
| Agility Health Radar | Structures many team dimensions | Can become unwieldy if there are too many dimensions |
| Echometer Health Checks | Combines measurement directly with retrospectives and actions | Effectiveness depends on honest reflection and follow-up |
Source: Agile Pulse 2020 by BearingPoint
Source: Great Place to Work study on agility in companies
Source: New Work Trafo Model by Me & Company
Health check retrospectives as a measurement instrument for agile maturity
Retrospectives are the best place to translate maturity measurement into improvement. The reason is simple: the data is discussed where the work happens.
If you want to get started right away, these health check retros are especially well suited.
Template 1: 5 Agile Values Health Check
This template is a good fit if you want to check whether Scrum values are really visible in everyday work: courage, respect, commitment, focus, and openness.
5 Agile Values Health Check: How the retro works
-
Random Icebreaker (2-5 minutes)
Echometer provides you with a generator for random check-in questions.
-
Review of open actions (2-5 minutes)
Before starting with new topics, you should talk about what has become of the measures from past retrospectives to check their effectiveness. Echometer automatically lists all open action items from past retros.
-
Health Check
All team members can answer the health checks anonymously on a scale. Then go through the results of the health checks together and record any additional comments if necessary. If you use the same health checks in several retrospectives, you can also track trends over time in Echometer.
- Courage: We value people showing courage.
- Respect: We value each other’s ideas, even when disagreeing.
- Commitment: Every team member is committed to follow through on what they have promised.
- Focus: We don’t allow ourselves to be distracted from reaching the sprint goal.
- Openness: We are open to constructive feedback and grow from it.
-
Discuss retro topics
Use the following open questions to collect your most important findings. First, everyone does it themselves, covered. Echometer allows you to reveal each column of the retro board individually in order to then present and group the feedback.
-
Catch-all question (Recommended)
So that other topics also have a place:
- What else would you like to talk about in the retro?
-
Prioritization / Voting (5 minutes)
On the retro board in Echometer, you can easily prioritize the feedback with voting. The voting is of course anonymous.
-
Define actions (10-20 minutes)
You can create a linked action via the plus symbol on a feedback. Not sure which measure would be the right one? Then open a whiteboard on the topic via the plus symbol instead to brainstorm root causes and possible measures.
-
Checkout / Closing (5 minutes)
Echometer enables you to collect anonymous feedback from the team on how helpful the retro was. This creates the ROTI score ("Return On Time Invested"), which you can track over time.
5 Agile Values Health Check
Health Check Questions (Scale)
Template 2: Team Morale Health Check
This template is useful if you want to measure maturity not only through processes, but also through energy, collaboration, and team climate.
Team Morale Health Check: How the retro works
-
Random Icebreaker (2-5 minutes)
Echometer provides you with a generator for random check-in questions.
-
Review of open actions (2-5 minutes)
Before starting with new topics, you should talk about what has become of the measures from past retrospectives to check their effectiveness. Echometer automatically lists all open action items from past retros.
-
Health Check
All team members can answer the health checks anonymously on a scale. Then go through the results of the health checks together and record any additional comments if necessary. If you use the same health checks in several retrospectives, you can also track trends over time in Echometer.
- Appreciation: My colleagues appreciate my contribution to the team.
- Team Spirit: There is a trusting working atmosphere in our team.
- Transparency: Everyone in my team knows who is currently working on what.
- Recovery & Breaks: I have enough room for breaks in which I can draw new energy.
- Meeting culture: Our meetings are well structured, yet leave room for creativity and new ideas.
- Support: In my team, each team member passes on their individual knowledge and experience.
-
Discuss retro topics
Use the following open questions to collect your most important findings. First, everyone does it themselves, covered. Echometer allows you to reveal each column of the retro board individually in order to then present and group the feedback.
-
Catch-all question (Recommended)
So that other topics also have a place:
- What else would you like to talk about in the retro?
-
Prioritization / Voting (5 minutes)
On the retro board in Echometer, you can easily prioritize the feedback with voting. The voting is of course anonymous.
-
Define actions (10-20 minutes)
You can create a linked action via the plus symbol on a feedback. Not sure which measure would be the right one? Then open a whiteboard on the topic via the plus symbol instead to brainstorm root causes and possible measures.
-
Checkout / Closing (5 minutes)
Echometer enables you to collect anonymous feedback from the team on how helpful the retro was. This creates the ROTI score ("Return On Time Invested"), which you can track over time.
Team Morale Health Check
Health Check Questions (Scale)
Template 3: Psychological Safety Health Check
Psychological safety is especially relevant when problems become visible late, decisions are glossed over, or retrospectives remain superficial.
Psychological Safety Health Check: How the retro works
-
Random Icebreaker (2-5 minutes)
Echometer provides you with a generator for random check-in questions.
-
Review of open actions (2-5 minutes)
Before starting with new topics, you should talk about what has become of the measures from past retrospectives to check their effectiveness. Echometer automatically lists all open action items from past retros.
-
Health Check
All team members can answer the health checks anonymously on a scale. Then go through the results of the health checks together and record any additional comments if necessary. If you use the same health checks in several retrospectives, you can also track trends over time in Echometer.
- If someone on our team makes a mistake, they are not held against it.
- In our team, difficult problems and uncomfortable topics can be addressed.
- No one on our team would intentionally act in a way that undermines my work.
- It is easy to ask other team members for help.
- My special skills and talents are valued and used in the team.
-
Discuss retro topics
Use the following open questions to collect your most important findings. First, everyone does it themselves, covered. Echometer allows you to reveal each column of the retro board individually in order to then present and group the feedback.
-
Catch-all question (Recommended)
So that other topics also have a place:
- What else would you like to talk about in the retro?
-
Prioritization / Voting (5 minutes)
On the retro board in Echometer, you can easily prioritize the feedback with voting. The voting is of course anonymous.
-
Define actions (10-20 minutes)
You can create a linked action via the plus symbol on a feedback. Not sure which measure would be the right one? Then open a whiteboard on the topic via the plus symbol instead to brainstorm root causes and possible measures.
-
Checkout / Closing (5 minutes)
Echometer enables you to collect anonymous feedback from the team on how helpful the retro was. This creates the ROTI score ("Return On Time Invested"), which you can track over time.
Psychological Safety Health Check
Health Check Questions (Scale)
You can find more formats in the overview of Retrospective methods .
Agile Maturity Assessment: Sample questions
A good Agile Maturity Assessment should be short enough for teams to repeat it, and concrete enough for actions to result from the answers.
Use statements that can be answered on a scale:
- Customer focus: We gather feedback from customers or stakeholders early enough.
- Predictability: We realistically assess how much work we can handle in parallel.
- Focus: Our team works toward clearly prioritized goals.
- Autonomy: We can make decisions within our area of responsibility ourselves.
- Feedback: Critical observations are addressed openly and constructively.
- Learning: Actions from retrospectives are tracked visibly.
- Quality: We reduce the root causes of errors instead of just fixing symptoms.
- Leadership: Our leaders help us clarify priorities and boundary conditions.
Common mistakes in maturity assessment
The most common mistakes are less methodological than cultural:
- Too many dimensions: No one knows anymore which change is really important.
- Team ranking: Teams optimize presentation instead of collaboration.
- Metrics without context: Velocity, lead time, or defects are misinterpreted.
- One-time survey: Without follow-up measurement, no learning cycle emerges.
- No retro linkage: Results stay in the dashboard instead of in the team discussion.
- Too large measures: Teams launch transformation packages that cannot be implemented in everyday work.
A good test: Can every team, after the assessment, say in one sentence which concrete experiment it will start next?
How companies promote agile maturity
After the assessment, the real work begins. These levers are almost always effective:
- Build trust: Strengthen transparency, clear decision-making spaces, and a constructive error culture.
- Realign leadership: Leaders should remove obstacles, clarify goals, and enable autonomy.
- Shorten feedback loops: Involve customers, stakeholders, and teams earlier and more often.
- Make retrospectives more binding: Every retro needs a few clear actions that are tracked.
- Learn across teams: Make good experiments visible without lumping teams together.
- Use one-to-one conversations: Regularly reflect on personal development, motivation, and obstacles.
For employee development, a recurring 1-to-1 health check can be helpful:
⁉️ Mood check (Agreement from 1-7): Personal development
- "My work tasks usually progress very quickly, even if external feedback is necessary."
- "When I observe suboptimal behavior, I know how to constructively point it out to colleagues."
- "I receive constructive feedback on both my work and my personal development."
- "I see an attractive career path ahead of me in the company." #Growth
- "In the last few weeks, I have very often been able to use my strengths at work."
This is what this survey looks like in Echometer:
Frequently asked questions about agile maturity measurement
How do you measure agile maturity?
Agile maturity is measured using a combination of team feedback, delivery metrics, quality data, and observable changes in behavior.
A practical sequence is:
- Define the goals of the agile transformation.
- Select 4 to 6 relevant dimensions, for example customer orientation, delivery, quality, team autonomy, learning culture, and leadership.
- Establish a baseline through a health check, metrics, and qualitative observation.
- Reflect on results in retrospectives.
- Derive 1 to 2 concrete actions per team.
- Measure again after 6 to 12 weeks and compare the progress within the same team.
Important: A maturity assessment is only useful if it is translated directly into improvement steps. A score alone does not improve agility.
What are the 5 stages of agile maturity?
A pragmatic 5-stage model for agile maturity looks like this:
- Reactive: Work is highly ad hoc, learning happens incidentally, and retrospectives have little impact.
- Repeatable: Agile rituals are in place, but quality and commitment fluctuate.
- Established: Team processes function reliably and improvements are implemented regularly.
- Data-driven: Decisions are backed by metrics, feedback, and observation.
- Learning: Continuous improvement is firmly anchored in the team and leadership culture.
The stages should serve as guidance, not as a rigid evaluation system. What matters is the trend within a team.
Which metrics are useful for measuring agile maturity?
Metrics from four perspectives are useful:
- Delivery: Lead time, delivery frequency, predictability.
- Quality: Defect rate, rework rate, technical stability.
- Team: Psychological safety, clarity, collaboration.
- Customer value: Feedback cycles, perceived added value, satisfaction.
- Improvement: implemented retro actions, removed blockers, tested experiments.
The key is the combination: individual metrics can be misinterpreted. Only the mix of hard and soft indicators provides a robust picture of the agile maturity level. Velocity is not suitable for team comparisons.
Wie oft sollte man den agilen Reifegrad messen?
In der Praxis ist ein Rhythmus von 6 bis 12 Wochen sinnvoll. So haben Teams genug Zeit, Maßnahmen umzusetzen, ohne dass die Messung zu selten wird.
Für eine erste Baseline reichen oft 3 Schritte:
- Kurzer Health Check.
- Reflexion in der Retrospektive.
- Nachmessung nach 1 bis 3 Sprint-Zyklen.
Monatliche Messungen können sinnvoll sein, wenn die Fragen sehr kurz sind. Zu häufige, lange Assessments führen dagegen schnell zu Umfragemüdigkeit.
Sollte man den agilen Reifegrad von Teams vergleichen?
Man sollte den agilen Reifegrad von Teams nicht als Ranking vergleichen. Teams arbeiten unter unterschiedlichen Bedingungen, zum Beispiel mit anderen Produkten, Abhängigkeiten, Legacy-Systemen oder Stakeholdern.
Sinnvoll ist ein Trendvergleich innerhalb desselben Teams: Hat sich der Wert seit der letzten Messung verbessert? Welche Maßnahme hat geholfen? Welche Blockade ist weiterhin sichtbar?
Teamübergreifende Muster können trotzdem wertvoll sein, wenn sie genutzt werden, um systemische Hindernisse zu erkennen, nicht um Teams zu bewerten.
Was ist der Unterschied zwischen agilem Reifegrad und Agile Maturity?
Agiler Reifegrad und Agile Maturity meinen im Kern dasselbe: Wie weit eine Organisation oder ein Team agile Prinzipien wirksam im Alltag lebt.
“Agiler Reifegrad” ist die deutsche Bezeichnung. “Agile Maturity” wird häufig in internationalen Frameworks, Assessments und Tools verwendet.
Wichtiger als der Begriff ist die Messlogik: Gute Agile-Maturity-Assessments messen nicht nur Prozesse, sondern auch Lernfähigkeit, Kundennähe, Zusammenarbeit, Qualität und Führung.
Welche Fragen gehören in ein Agile Maturity Assessment?
Gute Fragen in einem Agile Maturity Assessment sind konkret, beobachtbar und handlungsnah. Beispiele sind:
- Wir holen früh genug Feedback von Kund*innen oder Stakeholdern ein.
- Unser Team arbeitet an klar priorisierten Zielen.
- Wir können Entscheidungen in unserem Verantwortungsbereich selbst treffen.
- Kritische Beobachtungen werden offen und konstruktiv angesprochen.
- Maßnahmen aus Retrospektiven werden sichtbar nachverfolgt.
- Wir reduzieren Ursachen von Fehlern statt nur Symptome zu beheben.
Die Antworten sollten idealerweise auf einer Skala erhoben und anschließend in einer Retrospektive reflektiert werden.
Wie verbindet man agile Reifegradmessung mit Retrospektiven?
Agile Reifegradmessung lässt sich gut mit Retrospektiven verbinden, indem man Health-Check-Fragen vor oder zu Beginn der Retro beantwortet und die Ergebnisse direkt im Team reflektiert.
Der Ablauf ist einfach:
- Team beantwortet wenige Aussagen auf einer Skala.
- Ergebnisse werden in der Retrospektive sichtbar gemacht.
- Team diskutiert Auffälligkeiten und Ursachen.
- 1 bis 2 konkrete Maßnahmen werden beschlossen.
- In der nächsten Messung wird geprüft, ob sich etwas verbessert hat.
So bleibt die Messung nah an der täglichen Arbeit und wird nicht zu einem reinen Reporting-Instrument.
Conclusion
You measure agile maturity sensibly when you start with a clear goal and translate the data directly into actions and a learning loop. Start with a few dimensions, combine metrics with team feedback, discuss the results in team retrospectives, and measure again after 6 to 12 weeks.
The best indicator of agile maturity is not a perfect score, but a team’s ability to identify problems early and consistently implement effective improvements.
For more workshops on developing team culture and mindset, you will find additional inspiration in the free eBook: Teamflow & Mindset Change eBook
