Framework

Agile Maturity

A comprehensive view of agile maturity maturity across 10 domains, drawing on Scrum Guide, SAFe, XP, Kanban, DORA (Accelerate), Team Topologies & Lean Startup.

Each domain includes assessment questions mapping to five maturity levels, along with key strategy elements.

Maturity Scale

1
Initial

Ad hoc and reactive. No formal processes, reliant on individual effort.

2
Developing

Basic awareness and some repeatable processes emerging.

3
Defined

Documented standards and processes applied consistently.

4
Managed

Measured, monitored and controlled with quantitative targets.

5
Optimizing

Continuous improvement driven by data and innovation.

🧠

Agile Mindset & Culture

Agile Manifesto, Scrum Guide, Agile Fluency

The degree to which agile values and principles are understood, embraced and lived across the organization. Covers psychological safety, experimentation, and willingness to adapt.

Strategy Elements

Agile Values and Principles Training
Psychological Safety Assessment
Leadership Agile Coaching Program
Cultural Change Management Strategy
Experimentation and Innovation Framework
Agile Manifesto Alignment Review
Organizational Impediment Removal Process

Assessment Questions

1. How well are agile values and principles understood across your organization?

L1Little to no awareness of agile values; work is plan-driven and hierarchical
L2Some teams are aware of agile concepts but the wider org is not
L3Agile values are documented, trained and understood across most teams
L4Agile principles guide decision-making at all levels including leadership
L5Agile is deeply embedded in organizational DNA with continuous cultural reinforcement

2. How does your organization handle failure and experimentation?

L1Failure is punished; blame culture prevails
L2Some tolerance for failure in certain teams but not systematic
L3Psychological safety is promoted; failure is treated as a learning opportunity
L4Structured experimentation (hypothesis-driven) with blameless post-mortems
L5Continuous experimentation culture with rapid feedback and innovation rewarded

3. How does leadership support agile ways of working?

L1Leadership is directive and does not support agile practices
L2Some leaders are supportive but most still operate in command-and-control mode
L3Leadership actively supports agile and removes organizational impediments
L4Leaders model agile behaviors (servant leadership) and empower teams
L5Leadership drives agile transformation as a strategic capability
👥

Team Structure & Collaboration

Scrum Guide, SAFe, Team Topologies

How teams are formed, structured and collaborate. Covers cross-functional teams, self-organization, team stability, and inter-team coordination.

Strategy Elements

Cross-Functional Team Design
Team Topologies Assessment
Self-Organization Guidelines and Guardrails
Team Stability and Composition Strategy
Inter-Team Coordination Mechanisms
Dependency Management Process
Community of Practice Structure

Assessment Questions

1. How are your delivery teams structured?

L1Functional silos (dev, test, ops separate); handoffs between groups
L2Some cross-functional teams exist but many are still siloed
L3Most teams are cross-functional with all skills needed to deliver end-to-end
L4Stable, self-organizing cross-functional teams with clear team APIs
L5Teams dynamically form around value streams with Team Topologies principles

2. How autonomous are your teams in making decisions?

L1Teams have no autonomy; all decisions are made by managers
L2Teams can make some technical decisions but business decisions are top-down
L3Teams are empowered to make decisions within defined guardrails
L4Teams own their processes, tools and technical decisions with aligned goals
L5Full autonomy with mission-based teams accountable for outcomes, not output

3. How do teams collaborate and coordinate with each other?

L1No formal coordination; teams work in isolation with frequent conflicts
L2Ad hoc meetings when dependencies arise; often too late
L3Regular cross-team ceremonies (Scrum of Scrums, sync meetings)
L4Structured coordination with dependency management and shared planning
L5Seamless collaboration with minimal dependencies; architecture supports autonomy
🔄

Iterative Delivery & Planning

Scrum Guide, Kanban, SAFe, XP

How work is planned, executed and delivered in iterative cycles. Covers sprint/iteration management, release planning, estimation, and flow-based delivery.

Strategy Elements

Sprint/Iteration Framework
Release Planning and Cadence
Estimation and Forecasting Approach
Work-in-Progress Limits
Definition of Done
Demo and Review Process
Adaptive Planning at Multiple Horizons

Assessment Questions

1. How does your organization plan and deliver work?

L1Waterfall or big-bang delivery with long planning cycles (months/quarters)
L2Some teams use sprints but planning is still largely upfront and fixed
L3Consistent sprint/iteration cycles with regular planning and demos
L4Continuous flow with flexible planning horizons and frequent releases
L5Adaptive planning at all levels (portfolio, program, team) with continuous delivery

2. How frequently does your team deliver working software to users?

L1Rarely; large releases every few months or longer
L2Every few sprints; releases are batched and require significant coordination
L3At the end of each sprint (every 1-4 weeks)
L4Multiple times per sprint; small batch releases are routine
L5On demand; any commit can be deployed to production safely

3. How does your team handle estimation and forecasting?

L1No estimation or wildly inaccurate estimates with no tracking
L2Time-based estimates by individuals; often significantly off
L3Team-based relative estimation (story points) with velocity tracking
L4Probabilistic forecasting using historical data and cycle time metrics
L5Data-driven forecasting with Monte Carlo simulations and continuous refinement
🎯

Product Ownership & Backlog Management

Scrum Guide, Lean Startup, SAFe

How product vision, strategy, and backlogs are managed. Covers product ownership, prioritization, stakeholder alignment, and value-driven delivery.

Strategy Elements

Product Vision and Strategy Alignment
Product Owner Role Definition and Empowerment
Backlog Management and Refinement Process
Prioritization Framework (WSJF, MoSCoW, etc.)
User Research and Continuous Discovery
Outcome-Based Roadmapping
Stakeholder Engagement Model

Assessment Questions

1. How well-defined is product ownership in your organization?

L1No clear product owner; requirements come from multiple sources with conflicts
L2Product owner exists in name but lacks authority or availability
L3Empowered product owners with clear accountability for product decisions
L4Product owners are strategic, data-driven and deeply engaged with teams
L5Product leadership drives outcome-based roadmaps with portfolio alignment

2. How is the product backlog managed and prioritized?

L1No formal backlog; requirements are scattered in documents and emails
L2A backlog exists but is poorly maintained, rarely refined or too large
L3Well-groomed backlog with regular refinement and clear prioritization
L4Backlog is prioritized by value/risk/effort with data-driven decisions
L5Outcome-oriented backlog with continuous discovery and validated learning

3. How does your team validate that it is building the right thing?

L1No validation; features are built based on assumptions and delivered as-is
L2Some user feedback after delivery but rarely influences direction
L3Regular user demos and feedback sessions inform future work
L4Hypothesis-driven development with A/B testing and usage analytics
L5Continuous discovery with dual-track agile (discovery + delivery in parallel)

Technical Practices & Engineering Excellence

XP, Clean Code, Accelerate (DORA)

The technical practices that enable sustainable agility. Covers TDD, code quality, automated testing, refactoring, architecture for agility, and technical debt management.

Strategy Elements

Automated Testing Strategy (TDD/BDD)
Code Quality Standards and Reviews
Technical Debt Management Process
Architecture for Agility Principles
Pair/Mob Programming Practices
Refactoring and Clean Code Guidelines
Engineering Enablement and Developer Experience

Assessment Questions

1. How does your organization approach automated testing?

L1Little to no automated testing; manual testing is the norm
L2Some unit tests exist but coverage is low and tests are often skipped
L3Comprehensive test suites (unit, integration, e2e) run on every commit
L4TDD/BDD practiced with high coverage; tests are first-class citizens
L5Testing strategy continuously optimized; shift-left with contract and chaos testing

2. How is technical debt managed?

L1Technical debt is ignored; codebase is increasingly difficult to change
L2Technical debt is acknowledged but rarely addressed due to feature pressure
L3Technical debt is tracked and a percentage of capacity is allocated to address it
L4Technical debt is proactively managed with architecture fitness functions
L5Continuous refactoring culture; tech debt is minimized by design

3. How does your architecture support agile delivery?

L1Monolithic, tightly coupled systems that make changes slow and risky
L2Some modularization but significant coupling remains
L3Service-oriented architecture with clear boundaries enabling independent deployment
L4Microservices or modular architecture with evolutionary design principles
L5Architecture enables team autonomy with platform thinking and self-service capabilities
📈

Continuous Improvement

Scrum Guide, Lean, Toyota Kata

How teams and the organization inspect, adapt and improve. Covers retrospectives, kaizen, experimentation, process improvement, and organizational learning.

Strategy Elements

Retrospective Framework and Facilitation
Improvement Backlog and Tracking
Blameless Post-Mortem Process
Team Health Check Model
Improvement Metrics and KPIs
Kaizen / Toyota Kata Practices
Organizational Learning Strategy

Assessment Questions

1. How does your team practice retrospectives?

L1No retrospectives; the same problems keep recurring
L2Retrospectives happen occasionally but actions are rarely followed up
L3Regular retrospectives with tracked action items and follow-through
L4Retrospectives drive measurable improvements; diverse formats keep them effective
L5Continuous improvement is embedded in daily work, not just ceremonies

2. How does your organization learn from incidents and mistakes?

L1No post-incident process; same issues recur
L2Occasional post-mortems but findings are not widely shared
L3Blameless post-mortems with documented learnings and action items
L4Systematic learning with pattern analysis across incidents
L5Learning organization with proactive chaos engineering and resilience testing

3. How are process improvements identified and implemented?

L1No structured approach to process improvement
L2Improvements are suggested but implementation is inconsistent
L3Improvement backlog maintained with regular experiments
L4Data-driven improvement using flow metrics and team health checks
L5Continuous improvement culture with kata-style coaching and systemic thinking
🏢

Scaling & Organizational Agility

SAFe, LeSS, Spotify Model, Unfix

How agile practices scale beyond individual teams to the organization. Covers scaling frameworks, portfolio management, value streams, and organizational design.

Strategy Elements

Scaling Framework Selection and Adaptation
Value Stream Identification and Mapping
Lean Portfolio Management
Agile Budgeting and Funding Models
Organizational Design for Agility
Support Function Agile Enablement
Enterprise Agile Transformation Roadmap

Assessment Questions

1. How does agile scale across your organization?

L1Agile is limited to a few teams; the rest of the org works differently
L2Multiple teams use agile but coordination is ad hoc
L3A scaling framework is adopted with defined roles and ceremonies
L4Value stream-aligned teams with portfolio-level agile practices
L5Business agility at enterprise level; agile is how the organization operates

2. How is portfolio and investment management aligned with agile?

L1Annual budgets tied to projects with fixed scope and timeline
L2Some flexibility exists but funding is still project-based
L3Lean budgeting with funding allocated to value streams or products
L4Dynamic funding with regular portfolio reviews and pivot capability
L5Continuous funding flow with real-time portfolio optimization

3. How agile are your supporting functions (HR, finance, procurement)?

L1Supporting functions operate traditionally and create friction for agile teams
L2Some awareness of agile in support functions but little adaptation
L3Support functions have adapted key processes to enable agile delivery
L4Support functions actively partner with delivery using agile-friendly processes
L5Full business agility with all functions operating with agile principles
📊

Metrics & Transparency

Accelerate (DORA), Kanban, Evidence-Based Management

How performance is measured, visualized and used to drive improvement. Covers flow metrics, DORA metrics, outcome metrics, and information radiators.

Strategy Elements

Agile Metrics Framework (Flow, DORA, Outcome)
Information Radiators and Dashboards
Evidence-Based Management Approach
Velocity and Flow Metrics Best Practices
DORA Metrics Implementation
Outcome-Based Success Measures
Metrics Anti-Pattern Awareness

Assessment Questions

1. What metrics does your organization use to measure agile effectiveness?

L1No agile metrics; success is measured by on-time/on-budget delivery only
L2Velocity is tracked but often misused (e.g., as a productivity target)
L3Balanced metrics including flow (cycle time, throughput) and quality
L4DORA metrics tracked with outcome metrics (customer satisfaction, business value)
L5Evidence-based management with leading and lagging indicators driving strategy

2. How transparent is work status and progress?

L1Work status is opaque; stakeholders rely on status reports from managers
L2Some boards or tools exist but are not consistently updated
L3Visible boards (physical or digital) show real-time work status for all teams
L4Dashboards aggregate team, program and portfolio status with drill-down
L5Full transparency with self-service insights accessible to all stakeholders

3. How are metrics used to drive decisions and improvement?

L1Metrics are not used for decision-making
L2Metrics are collected but rarely analyzed or acted upon
L3Metrics are regularly reviewed in retrospectives and planning
L4Data-driven decisions at all levels with trend analysis and forecasting
L5Metrics drive autonomous improvement with AI-assisted insights
🤝

Stakeholder Engagement

Scrum Guide, SAFe, Lean UX

How stakeholders are engaged throughout delivery. Covers communication, feedback loops, expectation management, and collaborative partnership.

Strategy Elements

Stakeholder Communication Plan
Sprint Review and Demo Framework
Expectation Management Approach
User Feedback Loop Design
Collaborative Discovery Practices
Transparency and Reporting Cadence
Stakeholder Agile Education Program

Assessment Questions

1. How are stakeholders engaged in the delivery process?

L1Stakeholders only see results at the end of a project
L2Occasional demos but stakeholder feedback is rarely incorporated
L3Regular sprint reviews with active stakeholder participation and feedback
L4Stakeholders co-create with teams through ongoing discovery and validation
L5Deep partnership with embedded stakeholder collaboration throughout delivery

2. How does your organization manage expectations around scope, timeline and quality?

L1Fixed scope, fixed timeline; teams are pressured to deliver everything
L2Some negotiation possible but the iron triangle is still rigid
L3Scope is flexible; teams and stakeholders negotiate based on priorities
L4Outcome-based commitments with transparent trade-off discussions
L5Continuous value delivery with shared understanding that scope emerges

3. How effective are feedback loops between users and delivery teams?

L1No direct feedback loops; users are distant from delivery teams
L2Feedback comes through intermediaries (BAs, PMs) with delays
L3Direct user feedback through testing, surveys and regular touchpoints
L4Rapid feedback cycles with analytics, user research embedded in sprints
L5Real-time user telemetry and continuous discovery driving every decision
🚀

DevOps & Continuous Delivery

Accelerate (DORA), DevOps Handbook, SRE

The technical and cultural practices enabling continuous integration, delivery and deployment. Covers CI/CD pipelines, infrastructure automation, monitoring, and production ownership.

Strategy Elements

CI/CD Pipeline Architecture
Deployment Strategy (blue/green, canary, feature flags)
Infrastructure as Code Standards
Observability Strategy (logs, metrics, traces)
SLO/SLI/Error Budget Framework
Production Ownership Model
Platform Engineering and Developer Experience

Assessment Questions

1. How mature is your CI/CD pipeline?

L1No CI/CD; builds and deployments are manual and error-prone
L2Basic CI exists (automated builds) but deployment is still manual
L3Full CI/CD pipeline with automated testing and staging deployments
L4Continuous delivery to production with feature flags and canary releases
L5Continuous deployment with zero-downtime releases and automated rollback

2. How does your team approach production monitoring and observability?

L1No monitoring; issues are reported by users
L2Basic uptime monitoring and alerting for critical services
L3Comprehensive monitoring with logs, metrics and traces (three pillars)
L4Full observability with SLOs, error budgets and proactive alerting
L5AIOps with predictive monitoring, auto-remediation and chaos engineering

3. Who owns production in your organization?

L1Separate ops team owns production; devs throw code over the wall
L2Some shared responsibility but ops still handles most production issues
L3You build it, you run it — teams own their services in production
L4SRE practices with shared ownership, error budgets and toil reduction
L5Platform engineering enables full team ownership with self-service infrastructure

Strategy Checklist

A comprehensive strategy should address all of the following:

🧠 Mindset

  • Agile Values and Principles Training
  • Psychological Safety Assessment
  • Leadership Agile Coaching Program
  • Cultural Change Management Strategy
  • Experimentation and Innovation Framework
  • Agile Manifesto Alignment Review
  • Organizational Impediment Removal Process

👥 Teams

  • Cross-Functional Team Design
  • Team Topologies Assessment
  • Self-Organization Guidelines and Guardrails
  • Team Stability and Composition Strategy
  • Inter-Team Coordination Mechanisms
  • Dependency Management Process
  • Community of Practice Structure

🔄 Delivery

  • Sprint/Iteration Framework
  • Release Planning and Cadence
  • Estimation and Forecasting Approach
  • Work-in-Progress Limits
  • Definition of Done
  • Demo and Review Process
  • Adaptive Planning at Multiple Horizons

🎯 Product

  • Product Vision and Strategy Alignment
  • Product Owner Role Definition and Empowerment
  • Backlog Management and Refinement Process
  • Prioritization Framework (WSJF, MoSCoW, etc.)
  • User Research and Continuous Discovery
  • Outcome-Based Roadmapping
  • Stakeholder Engagement Model

Engineering

  • Automated Testing Strategy (TDD/BDD)
  • Code Quality Standards and Reviews
  • Technical Debt Management Process
  • Architecture for Agility Principles
  • Pair/Mob Programming Practices
  • Refactoring and Clean Code Guidelines
  • Engineering Enablement and Developer Experience

📈 Improvement

  • Retrospective Framework and Facilitation
  • Improvement Backlog and Tracking
  • Blameless Post-Mortem Process
  • Team Health Check Model
  • Improvement Metrics and KPIs
  • Kaizen / Toyota Kata Practices
  • Organizational Learning Strategy

🏢 Scaling

  • Scaling Framework Selection and Adaptation
  • Value Stream Identification and Mapping
  • Lean Portfolio Management
  • Agile Budgeting and Funding Models
  • Organizational Design for Agility
  • Support Function Agile Enablement
  • Enterprise Agile Transformation Roadmap

📊 Metrics

  • Agile Metrics Framework (Flow, DORA, Outcome)
  • Information Radiators and Dashboards
  • Evidence-Based Management Approach
  • Velocity and Flow Metrics Best Practices
  • DORA Metrics Implementation
  • Outcome-Based Success Measures
  • Metrics Anti-Pattern Awareness

🤝 Stakeholders

  • Stakeholder Communication Plan
  • Sprint Review and Demo Framework
  • Expectation Management Approach
  • User Feedback Loop Design
  • Collaborative Discovery Practices
  • Transparency and Reporting Cadence
  • Stakeholder Agile Education Program

🚀 DevOps

  • CI/CD Pipeline Architecture
  • Deployment Strategy (blue/green, canary, feature flags)
  • Infrastructure as Code Standards
  • Observability Strategy (logs, metrics, traces)
  • SLO/SLI/Error Budget Framework
  • Production Ownership Model
  • Platform Engineering and Developer Experience