In short
The AI-delivery capability check uses the seven capabilities from the DORA Report 2025 to score whether an organization can amplify delivery with AI. The core finding: AI is an amplifier, not a repair tool — existing maturity decides whether AI raises throughput or destroys stability. The self-assessment gives levels, diagnostics and quick wins.
Why This Capability Check Matters Now
Nearly every engineering team now uses AI assistance in software delivery; according to the DORA Report 2025, around 90% of the developers surveyed use AI tools in their daily work. The report delivers the sobering key insight: artificial intelligence is an amplifier, not a repair tool. It noticeably increases throughput — but without mature delivery foundations, it simultaneously degrades stability. AI makes a well-positioned organization faster and a poorly positioned organization faster at breaking.
Where your organisation stands across the seven capabilities is answered by the free AI readiness check in about 3 minutes — including a score and prioritised actions.
This is precisely where this self-assessment comes in. We designed it so you can run it immediately with your team: no theory, but seven concrete capabilities, each with maturity levels, diagnostic questions, common gaps, and immediate actions. The goal is not an overall grade but a differentiated picture of which foundations carry your AI investment — and which currently undermine it.
This article turns the DORA Report 2025 into practice: it explains why AI amplifies rather than repairs, places the report's seven team profiles, and is at the same time a repeatable instrument with which you measure your position across the seven capabilities. It complements the AI Readiness Assessment, which examines organizational AI preparedness at the enterprise level, and the DevOps Maturity Assessment, which evaluates general delivery maturity independent of the AI context.
Our recommendation: read all seven capabilities once in full, rate each on the five-level scale, and conduct the check with at least three people from different roles — development, operations, and product. A capability check filled out by a single person has blind spots.
The central thesis of the DORA Report 2025: AI amplifies the existing system. Teams with mature foundations gain throughput and keep stability. Teams without those foundations also gain throughput — while losing reliability at the same time. Maturity is the variable that determines the sign of the AI effect.
The Maturity Model Behind the Check
Each of the seven capabilities is rated on a consistent five-level scale. The levels are cumulative — a higher level presupposes that the one below is consistently achieved. Skipping levels is neither possible nor sensible.
The levels are: Level 1 — Ad-hoc (no deliberate practice, success depends on individuals). Level 2 — Initial (first deliberate attempts, inconsistently applied). Level 3 — Defined (standardized and practiced organization-wide). Level 4 — Managed (measured and optimized data-driven). Level 5 — Optimizing (continuous, proactive improvement with short feedback loops).
Rate conservatively. A capability is only at a level if that level is the normal case — not the exception an engaged team reaches in good weather. When in doubt, choose the lower level. An honest Level 2 profile is more valuable than an inflated Level 4 profile, because only the honest profile leads to effective actions.
Rule of thumb for level placement: Would this practice still work if the most experienced person on the team were on vacation for two weeks? If not, you are at Level 2 at most — regardless of how good it looks on good days.
Capability 1 & 2: Clear AI Stance and Healthy Data Ecosystems
The first two capabilities of the DORA AI Capabilities Model govern the conditions under which AI is used and the data foundation it works on. The capability names and content follow the DORA survey questions; the maturity levels are an editorial operationalization for this check.
Capability 1 — Clear and Communicated AI Stance
Definition: Everyone knows which AI tools are allowed and what AI may and may not be used for. The AI policy actually applies to daily work, the organization supports experimentation, and knowledge is shared through training or demos.
Maturity levels: Level 1 — no rules, everyone uses arbitrary tools or abstains out of uncertainty. Level 2 — informal recommendations, scope unclear. Level 3 — approved tools, documented policy, training. Level 4 — the policy is reviewed regularly, exchange formats are established. Level 5 — stance and policy are continuously sharpened based on experience and outcomes.
Common gap: a policy exists, but the team does not know whether it applies to its own work — the result is shadow tools or unused licenses. Immediate action: one page naming approved tools, allowed and excluded use cases, and the handling of sensitive data, plus a fixed slot for exchange or demos.
Capability 2 — Healthy Data Ecosystems
Definition: Internal data is easy to access and analyze, not trapped in silos, and of reliable quality. Anyone who needs a data point gets a definitive answer quickly.
Maturity levels: Level 1 — data sits in isolated silos, quality is unknown. Level 2 — central data sources exist, but currency and quality are not assured. Level 3 — data quality is monitored, access is governed and documented. Level 4 — data quality metrics are actively managed, lineage is traceable. Level 5 — self-healing data pipelines, quality is embedded in the workflow.
Common gap: AI-supported analysis and code generation produce plausible-looking but factually wrong results because the underlying data is stale or inconsistent. Immediate action: identify the three data sources AI tools or dashboards rely on most, and for each check: who is responsible, when was it last validated, how is quality measured?
Capability 3 & 4: AI-Accessible Internal Data and Strong Version Control
The next two capabilities determine whether AI works with the right context and whether its contributions can be traced and reverted.
Capability 3 — AI-Accessible Internal Data
Definition: AI tools can use internal sources such as codebases, databases, wikis and work management systems as context — in a permission-compliant and traceable way.
Maturity levels: Level 1 — AI works without internal context, content is pasted in manually. Level 2 — individual tools access the codebase, other sources are missing. Level 3 — codebase, documentation and ticket system are connected, permissions are governed. Level 4 — access is logged, the quality of context use is reviewed. Level 5 — new data sources are opened up deliberately and in a controlled way.
Common gap: AI produces generic suggestions that ignore internal conventions and interfaces, or internal data flows uncontrolled into external tools. Immediate action: define which internal sources each tool may use, and connect the most important source — usually codebase and documentation — in a controlled way.
Capability 4 — Strong Version Control Practices
Definition: Application code, application and system configurations, build automation and prompts for AI systems are kept in version control. Changes are committed frequently and can be reverted routinely.
Maturity levels: Level 1 — only parts of the code are versioned, configurations live outside. Level 2 — code is versioned, configurations and prompts are not. Level 3 — all of these artifacts are versioned, reverts are possible. Level 4 — AI-generated contributions are traceable, reverts are practiced routine. Level 5 — versioning and reverting are so natural that they actively ease experimentation.
Common gap: prompts and configurations are maintained outside version control — after a faulty AI-assisted change it is unclear what changed. Immediate action: check for the main service whether code, configuration, build automation and prompts are versioned, and close the first gap.
Capability 5, 6 & 7: Small Batches, User-Centric Focus and Internal Platform
The last three capabilities determine whether AI-accelerated work stays manageable, creates value and is carried by the technical base.
Capability 5 — Working in Small Batches
Definition: Tasks are short, commits are small, and a deployment contains only a few changes.
Maturity levels: Level 1 — large batch releases with many changes. Level 2 — smaller releases, but large pull requests. Level 3 — tasks are deliberately cut small, pull requests are manageable. Level 4 — batch sizes are measured, large changes stand out. Level 5 — small batches are the normal case, including for AI-generated changes.
Common gap: AI produces large diffs faster than review capacity grows; reviewers wave through what they have not fully understood. Immediate action: define an upper limit for the size of AI-assisted pull requests and a comprehension checkpoint before merge.
Capability 6 — User-Centric Focus
Definition: User value is the focus, the team understands what users want to accomplish, and user feedback is used to continuously reprioritize features.
Maturity levels: Level 1 — user need is assumed, not gathered. Level 2 — occasional user interviews without systematic evaluation. Level 3 — user feedback is a fixed part of prioritization. Level 4 — behavioral data is correlated with deployment events. Level 5 — continuous experiments (A/B, feature flags) steer product decisions.
Common gap: AI accelerates building features whose value was never validated — the organization produces faster past its users. Immediate action: for the last five delivered features, check whether a measurable user signal was defined for each and whether that signal is being tracked.
Capability 7 — Quality Internal Platform
Definition: The internal platform abstracts away infrastructure complexity, gives clear feedback on the outcome of tasks, automates routine work, and helps teams build reliable, secure services and follow required processes. The platform team acts on feedback.
Maturity levels: Level 1 — every team builds its own infrastructure, high friction. Level 2 — shared scripts and templates, but no self-service. Level 3 — internal platform with self-service for the most common paths. Level 4 — platform adoption and developer experience are measured and managed. Level 5 — the platform evolves data-driven based on usage signals, friction is systematically removed.
Common gap: AI generates more deployments, but each deployment runs through a high-friction, manual path — the bottleneck shifts from writing code to delivering it. Immediate action: measure the time a new team member needs until the first productive deployment. More than one day indicates a weak platform capability.
Complementary Practices: Important, but Not a DORA Capability
The following practices are not among the seven capabilities of the DORA AI Capabilities Model. As an editorial recommendation they remain relevant, because they safeguard the higher rate of change that AI assistance produces.
- Test automation and quality gates: automated tests as a mandatory pipeline component, review as standard and, for AI-generated code, a comprehension checkpoint before merge.
- Fast feedback loops: CI and observability detect regressions early; a useful check is the time between delivery and detection for recent incidents.
- Measurable AI governance: two metrics from which the effect of AI use on quality and throughput can be read regularly.
- Clear specifications: documented requirements as a shared reference point for humans and AI.
The 7-Capabilities Maturity Matrix at a Glance
The following matrix summarizes the seven capabilities and their characteristic expressions per maturity level. Use it as a rating grid: for each row, mark the level that describes the normal case for your organization — not the best day.
How to read the matrix: the AI effect does not tip at a single capability but at the weakest one. An organization with six capabilities at Level 4 and one at Level 1 experiences the AI damage precisely through that one gap — which one that is, only your own profile shows.
| Capability | Level 1-2 (Ad-hoc/Initial) | Level 3 (Defined) | Level 4-5 (Managed/Optimizing) |
|---|---|---|---|
| 1 AI Stance | No or unclear rules, sprawl or reluctance | Approved tools, policy, training | Policy sharpened regularly, exchange established |
| 2 Data Ecosystems | Silos, quality and currency unknown | Data quality monitored, access governed | Lineage traceable, quality embedded in workflow |
| 3 AI-Accessible Data | AI without internal context, copy-and-paste | Codebase, docs and tickets connected, permissions governed | Access logged, sources expanded in a controlled way |
| 4 Version Control | Only parts of the code versioned | Code, configuration, build automation and prompts versioned | Reverts are routine, AI contributions traceable |
| 5 Small Batches | Batch releases, large pull requests | Tasks deliberately cut small | Batch size measured, small batches the normal case |
| 6 User-Centric Focus | User need assumed, not gathered | User feedback a fixed part of prioritization | Continuous experiments steer product decisions |
| 7 Internal Platform | Each team builds its own infrastructure, high friction | Self-service for the most common paths | Platform evolves data-driven, friction minimized |
The 7 Team Profiles of the DORA Report 2025: Where Does Your Team Stand?
Instead of sorting teams into the Elite-to-Low tiers, the DORA Report 2025 describes seven team profiles (archetypes). They rest on three dimensions: throughput, instability and team well-being, such as burnout and friction. The practical value lies not in the label but in the diagnosis: each profile points to a different next step.
The overview uses the official profile names. Shares appear only where summaries of the report (Splunk, Scrum.org) quantify them; together, roughly 40% land in the two strongest profiles. The "Recommended next step" column is an editorial derivation, not a statement of the report. Many teams recognize themselves in hybrid forms.
Which Profile Fits Your Team?
An honest self-classification works through three guiding questions along the dimensions the profiles rest on.
- Throughput question: How are change lead time, deployment frequency and failed deployment recovery time developing? Low cadence with high quality points to "High impact, low cadence" or "Stable and methodical", low throughput with heavy coordination overhead to "Constrained by process".
- Instability question: Are change fail rate or deployment rework rate rising, for instance since AI was introduced? Constantly reacting to unstable legacy systems points to "The legacy bottleneck", widespread process gaps under high strain to "Foundational challenges".
- Well-being question: How do burnout, friction and trust look in the team? Fast and stable with only average well-being matches "Pragmatic performers", fast and stable with high well-being "Harmonious high-achievers".
- Aggregation: The profile matching the most honestly answered questions is your realistic starting point. What matters is not perfect categorization but the derived priority for the next step.
| Team Profile | Characteristic | Recommended Next Step |
|---|---|---|
| Foundational challenges (~10%) | Survival mode: process gaps, high strain, unstable systems | Harden the foundation first (tests, version control, pipeline), then expand AI adoption |
| The legacy bottleneck (~11%) | Constantly reacting to unstable legacy systems | Prioritize stability over speed, repair incident and feedback mechanics, decouple legacy systems step by step |
| Constrained by process | Consumed by inefficient workflows | Analyze the value stream, cut manual handoffs and approvals, reduce platform friction |
| High impact, low cadence | High-quality work, but slow | Reduce batch size and raise cadence without giving up the existing safety nets |
| Stable and methodical | Deliberate, high quality | Introduce AI deliberately, but couple it to the existing tests and reviews |
| Pragmatic performers (~20%) | Fast and stable, well-being and trust only average | Reduce friction and strain in the team, measure well-being alongside the metrics |
| Harmonious high-achievers (~20%) | Fast, stable and high well-being | Lock in progress, formalize AI governance, scale practices |
The Self-Check: 12 Diagnostic Questions
Answer the following twelve questions as a team, honestly and conservatively. Each question is phrased so that a hesitant or evasive answer is already the answer. Note the associated capability number for each question — this yields your gap profile.
Evaluation rule: every question you cannot answer with a clear, evidenced "yes" counts as a gap in the associated capability. Three or more gaps in the same capability mean: that capability is at Level 2 at most — regardless of how it feels.
- Can every team member say which AI tools are allowed and what AI may and may not be used for? (Capability 1)
- Does the AI policy visibly apply to the team's work, and is there organized support for experimentation, such as training or demos? (Capability 1)
- Does the team get a definitive answer within one hour for an internal data point it needs, without being blocked by data silos? (Capability 2)
- For the three most important data sources, do you know who is responsible and when they were last validated? (Capability 2)
- Do the AI tools in use have permission-compliant access to internal sources such as codebase, wiki and ticket system? (Capability 3)
- Is it traceable which internal data goes to which AI tools? (Capability 3)
- Are application code, configurations, build automation and prompts for AI systems fully kept in version control? (Capability 4)
- Can every change, including an AI-generated one, be reverted quickly and routinely? (Capability 4)
- Does a typical deployment contain only a few changes, and is a typical task completed in under one day? (Capability 5)
- Is there an enforced size limit and a comprehension checkpoint for AI-assisted pull requests? (Capability 5)
- For the last five features, was a measurable user signal defined and tracked for each? (Capability 6)
- Does the internal platform offer self-service and clear feedback, and does a new team member need less than one day to the first productive deployment? (Capability 7)
Scoring Approach: From Profile to Priority
A single overall score is deliberately not the goal of this check. An average across seven capabilities obscures exactly the one weak capability through which AI causes damage. We instead recommend a three-step approach.
The most effective single action after this check is almost never "more AI" — it is closing the lowest capability gap. Only when no capability remains at Level 1 does additional AI acceleration reliably pay into throughput without costing stability.
- Build the profile: for each of the seven capabilities, enter the determined level (1-5). The result is a profile of seven values, ideally visualized as a radar chart. What becomes visible is not an average but the shape of your maturity — and in particular the deepest dip.
- Identify the bottleneck: mark the lowest capability. It is your AI risk driver, because the negative stability effect of AI materializes along the weakest capability, not along the average. If the lowest capability is at Level 1-2, aggressive AI speed is dangerous until this gap is closed.
- Derive the sequence: first raise every capability at Level 1 to at least Level 2 — this removes the acute damage vectors. Then invest specifically in the capability with the greatest business relevance instead of optimizing broadly. Address a maximum of three capabilities at a time.
- Set the repetition cadence: fix the next assessment date in advance (recommendation: every six months). Only repetition turns the check from a snapshot into a steering mechanism and makes progress evidenced.
Positioning Within Your Assessment Portfolio
This AI-delivery capability check is deliberately scoped tightly to the question of whether your foundations carry AI gains. It unfolds its full effect in combination with two further instruments.
The AI Readiness Assessment examines organizational AI preparedness at the enterprise level — strategy, data, competencies, governance — and provides the strategic frame into which this delivery-specific check is embedded. The DevOps Maturity Assessment evaluates general delivery maturity across culture, automation, processes, measurement, and security, independent of the AI context, and serves as a broader baseline. The research foundation for why exactly these seven capabilities make the difference is the DORA Report 2025 itself (sources below).
Our recommendation for practice: start with this check as a fast, focused self-assessment for a pilot team. Use the identified weakest capability as a concrete entry point. Then expand with the DevOps Maturity Assessment for the complete delivery picture and the AI Readiness Assessment for the enterprise perspective.
Sources & References
The capabilities, maturity logics, and findings referenced in this article are based on the following sources:
- Google Cloud — Announcing the 2025 DORA Report: https://cloud.google.com/blog/products/ai-machine-learning/announcing-the-2025-dora-report
- Google Cloud — 2025 DORA AI-Assisted Software Development Report: https://cloud.google.com/resources/content/2025-dora-ai-assisted-software-development-report
- InfoQ — AI Is Amplifying Software Engineering Performance (DORA 2025): https://www.infoq.com/news/2026/03/ai-dora-report/
- RedMonk — DORA 2025: Measuring Software Delivery After AI: https://redmonk.com/rstephens/2025/12/18/dora2025/
- DORA — DevOps Research and Assessment: https://dora.dev/
- DORA — AI Capabilities Model (survey questions): https://dora.dev/ai/capabilities-model/questions/
- Splunk — State of DevOps 2025 (team profiles and shares): https://www.splunk.com/en_us/blog/learn/state-of-devops.html
- Scrum.org — DORA Report 2025 Summary: https://www.scrum.org/resources/blog/dora-report-2025-summary-state-ai-assisted-software-development
Key Takeaways
- According to the DORA Report 2025, AI is an amplifier, not a repair tool — existing maturity determines whether AI increases throughput or destroys stability.
- Seven capabilities amplify the AI benefit according to the DORA AI Capabilities Model: clear and communicated AI stance, healthy data ecosystems, AI-accessible internal data, strong version control practices, working in small batches, user-centric focus, and a quality internal platform.
- Rate each capability conservatively on a five-level scale — a practice only counts if it is the normal case, not the good day.
- AI damage materializes along the weakest capability, not along the average — which is why a profile is more meaningful than an overall score.
- The most effective action after the check is almost never "more AI" but closing the lowest capability gap.
- Repeat the check on a planned six-month cadence — only repetition turns it into a steering mechanism rather than a snapshot.
Frequently Asked Questions
The AI-delivery capability check is a structured self-assessment that operationalizes the seven capabilities from the DORA Report 2025. Each capability — clear and communicated AI stance, healthy data ecosystems, AI-accessible internal data, strong version control practices, working in small batches, user-centric focus, and a quality internal platform — is rated on a five-level scale. The result is not an overall score but a profile that shows which foundations carry your AI investment and which currently undermine it. The check provides a definition, maturity levels, diagnostic questions, common gaps, and immediate actions per capability and is designed as a repeatable steering instrument, not a one-time exam.
The DORA Report 2025 shows that AI assistance increases throughput, but the impact on delivery stability depends on the maturity of the organization. Teams with mature foundations — such as strong version control, small batches and a quality internal platform — gain speed and keep stability. Teams without those foundations also gain speed but simultaneously lose reliability, because AI scales the existing rate of change and therefore existing weaknesses too. AI is thus a lever that amplifies the sign of existing maturity — positive as well as negative. Which of the report's seven team profiles applies to you is covered in the section on team profiles.
The DevOps Maturity Assessment evaluates general delivery maturity across five dimensions — culture, automation, processes, measurement, and security — independent of the AI context. It is the broader baseline for the entire software delivery organization. The AI-delivery capability check is narrower and more specific: it asks only whether your foundations carry the gains from AI assistance, and operationalizes the seven capabilities from the DORA Report 2025 for this purpose. The two complement each other: the DevOps Maturity Assessment provides the complete delivery picture, this check focuses on the AI-specific risk question. We recommend starting with this check as a fast entry point and using the DevOps Maturity Assessment for the comprehensive baseline.
The AI Readiness Assessment examines AI preparedness at the enterprise level — strategy, data foundation, competencies, governance, and organizational preconditions. It answers the question of whether the organization as a whole is ready for AI. The AI-delivery capability check is the delivery-specific deep dive within that frame: it concretely tests whether the software delivery foundations carry the AI gains. In practice, the AI Readiness Assessment provides the strategic frame, this check the operational depth for the engineering organization. Ideally, you use both in combination.
We recommend a six-month cadence. Only planned repetition turns the check from a snapshot into a steering mechanism that makes progress evidenced. A semi-annual rhythm fits typical planning cycles and at the same time gives enough time for improvement measures — particularly on cultural and process capabilities — to take effect. More frequent than every six months is rarely useful; less frequent than annually risks losing the improvement momentum. Our tip: fix the next date bindingly in advance, otherwise it gets postponed by day-to-day operations.
Identify the lowest capability in the profile and close that gap first — do not raise the average, do not optimize broadly. The negative stability effect of AI materializes along the weakest capability, not along the mean. As long as even one capability is at Level 1, aggressive AI speed is risky. Therefore raise every Level 1 capability to at least Level 2 as a priority, then invest specifically in the capability with the greatest business relevance. Never address more than three capabilities at a time to avoid overload and half-heartedness.
Yes. The check is deliberately designed as a self-assessment and can be run in a few hours with your own team. It is important not to have a single person fill it out — involve at least three people from development, operations, and product to reduce blind spots, and rate conservatively. The typical self-bias is to rate yourself too positively in areas perceived as unimportant and too critically in areas that are currently frustrating. For the first organization-wide assessment, neutral external facilitation can help correct bias and bring in industry benchmarks — for the ongoing semi-annual repetition, the self-assessment mode is usually sufficient.
Through three guiding questions along the dimensions the seven profiles rest on. First, throughput: how are lead time, deployment frequency and failed deployment recovery time developing? Second, instability: are change fail rate or deployment rework rate rising, for instance since AI was introduced? Third, well-being: how do burnout, friction and trust look in the team? Fast and stable with high well-being matches "Harmonious high-achievers", with only average well-being "Pragmatic performers"; constantly reacting to unstable legacy systems points to "The legacy bottleneck". What matters is not perfect categorization but the derived priority for the next step.