Frameworks

maturity / assessment / agile

Agile Maturity Radar

An evidence-led radar, current and target scores, and a gap-ordered improvement plan.

Purpose

Build an evidence-led picture of working practices and choose the next useful improvement. Compare against an agreed baseline, not an invented industry league table.

When to use

  • Teams want a shared improvement baseline.
  • A change programme needs evidence of capability development.

What you get

  • Maturity dimensions with evidence scoring criteria.
  • A radar review structure and baseline comparison guide.

How to use Agile Maturity Radar

Quick start

  1. 1Score dimensions with evidence, not aspiration.
  2. 2View the radar.
  3. 3Take the largest evidence-backed gap as the only improvement theme for 30 days.

What good looks like

Every score cites an artefact or observed behaviour, the plan is gap-ordered, and there is no level-4 vanity without proof.

Common mistakes

  • Scoring for a sponsor audience.
  • Benchmarking to an invented industry league table.
  • Ten improvement themes at once.

Capability profile

Scale 1 to 5

0102030405060708
CurrentTarget
  1. 01CI/CD & Automation
  2. 02Code Quality
  3. 03Iterative Planning
  4. 04Flow & WIP
  5. 05Psychological Safety
  6. 06Continuous Learning
  7. 07Servant Leadership
  8. 08Strategic Alignment

Monday action: Pick one dimension; write the evidence you already have and the evidence you lack.

Interactive workspace

Open tools / your team's context

Local workspace

Agile maturity workspace

Editable local examples, not industry benchmarks.

Loading local workspace

Current average
2.5 / 5
Below target
8
Evidence recorded
8

Capability profile

Scale 1 to 5

0102030405060708
CurrentTarget
  1. 01CI/CD & Automation
  2. 02Code Quality
  3. 03Iterative Planning
  4. 04Flow & WIP
  5. 05Psychological Safety
  6. 06Continuous Learning
  7. 07Servant Leadership
  8. 08Strategic Alignment

Improvement plan, largest gaps first

Code Quality

2 → 4

Agree a short review checklist and test it on the next change.

Flow & WIP

2 → 4

Set a WIP limit and agree a backup reviewer.

Continuous Learning

2 → 4

Review the previous retrospective action before starting a new one.

Strategic Alignment

2 → 4

Link the next three changes to the reliability objective.

CI/CD & Automation

3 → 4

Add a failed-payment scenario to the deployment checks.

Iterative Planning

3 → 4

Bring one customer outcome into the planning conversation.

Psychological Safety

3 → 4

Ask for dissenting views before agreeing a release decision.

Servant Leadership

3 → 4

Choose one recurring dependency to remove this month.

Apply this with a practitioner

Engage Email hello@momentup.co.uk

Free to use and adapt with attribution to Momentup Consulting under Creative Commons Attribution 4.0 (CC BY 4.0). Read the licence.

Apply it with our practitioners

Get in touchEngage