---
title: Capabilities in DORA Core Model
tags: 
author: [asato](https://convert.docswell.com/user/at_946)
site: [Docswell](https://www.docswell.com/)
thumbnail: https://bcdn.docswell.com/page/L7LK6VNQER.jpg?width=480
description: 会社の勉強会で使ったDORA Core ModelのCapabilitiesのまとめ。 Capabilitiesなどの概念に興味を持ってもらうための資料です。
published: March 28, 25
canonical: https://convert.docswell.com/s/at_946/KWWY18-2025-03-28-160331
---
# Page. 1

![Page Image](https://bcdn.docswell.com/page/L7LK6VNQER.jpg)

Capabilities in DORA Core Model


# Page. 2

![Page Image](https://bcdn.docswell.com/page/4EM25GQKEW.jpg)

DORA Core Model
This model is built by DORA team based on their research
They have annually published Accelerate State of DevOps Report
This model shows that:
i. Technical and Cultural Capabilities drive Organizational Performance
ii. Better Organizational Performance can lead to Better Organizational Outcomes


# Page. 3

![Page Image](https://bcdn.docswell.com/page/PERM3Z8679.jpg)

DORA Core Model
Outcomes indicate whether we are developing EFFECTIVE products
Performance indicates whether we are developing products EFFECTIVELY
Capabilities indicate clues to improve our performance


# Page. 4

![Page Image](https://bcdn.docswell.com/page/P7XV498DJX.jpg)

Improvement Cycle
with DORA Core Model
1. Measure &quot;Performance&quot; (Four Key Metrics)
2. Decide which &quot;Capabilities&quot; should be improved
3. Implement the actions to improve the &quot;Capabilities&quot;
4. Measure &quot;Performance&quot; again
5. Repeat the cycle


# Page. 5

![Page Image](https://bcdn.docswell.com/page/37KQZPKD7D.jpg)

Capabilities
18 capabilities are found in DORA Core Model
Are grouped into 3 categories:
Climate for Learning
Fast Flow
Fast Feedback


# Page. 6

![Page Image](https://bcdn.docswell.com/page/LJ3PDXZP75.jpg)

Climate for Learning
is the atmosphere and the environment that foster the
culture of continuous improvement and knowledge sharing
Capabilities
1. Code Maintainability
2. Documentation Quality
3. Empowering Teams To Choose Tools
4. Generative Cultures


# Page. 7

![Page Image](https://bcdn.docswell.com/page/8JDLP2R37G.jpg)

Example: Team Without Climate for Learning
Common symptoms:
You have no reliable documents. Documentation is outdated or non-existent
Knowledge is siloed with individual team members
New team members take months to become productive
Same mistakes happen repeatedly
Resistance to trying new things and then they give up improvement
Code becomes increasingly difficult to maintain
High stress during deployments or incidents
Blame culture over learning from failures


# Page. 8

![Page Image](https://bcdn.docswell.com/page/VEP2N1WPE8.jpg)

Fast Flow
is a collection of approaches that enables teams to achieve
extreme focus and productivity
Capabilities
1. Continuous Delivery
2. Database Change
Management
3. Deployment Automation
4. Flexible Infrastructure
5. Loosely Coupled Teams
6. Streamlining Change
Approval
7. Version Control
8. Working in Small Batches


# Page. 9

![Page Image](https://bcdn.docswell.com/page/27VDKY8V7Q.jpg)

Example: Team Without Fast Flow
Common symptoms:
Deployments are manual and error-prone
Large batches of changes deployed infrequently, and they miss the opportunity to
deliver value to customers
Multiple teams need to coordinate for every release
Database changes cause incidents frequently
Long approval chains delay deployments
Teams are blocked waiting for other teams
Infrastructure changes require tickets and long wait times


# Page. 10

![Page Image](https://bcdn.docswell.com/page/5JGYQ951JL.jpg)

Fast Feedback
Ensures that the team receives rapid, actionable insights
throughout the entire software delivery lifecycle
Capabilities
1. Continuous Integration
2. Monitoring and Observability
3. Resilience Engineering
4. Pervasive security
5. Test Automation
6. Test Data Management


# Page. 11

![Page Image](https://bcdn.docswell.com/page/47QMKWZNEP.jpg)

Example: Team Without Fast Feedback
Common symptoms:
high anxiety and stress due to lack of confidences in tests
Production incidents frequently occur and take days to resolve
Features take months to reach customers due to lengthy testing and debugging
cycles
Customers report bugs and performance issues before the team discovers them
Engineers spend more time fighting fires than building features
Teams waste hours in emergency meetings and blame games after each incident
Security vulnerabilities remain for long periods


# Page. 12

![Page Image](https://bcdn.docswell.com/page/KE4VPK3371.jpg)

Takeaway
DORA Core Model shows that Technical and Cultural Capabilities drive
Organizational Performance &amp; Outcomes
There are 18 capabilities that are grouped into 3 categories:
Climate for Learning
Fast Flow
Fast Feedback
If you want to know more about the capabilities, please refer to:
DORA Core Model
DORA Capability Catalog


# Page. 13

![Page Image](https://bcdn.docswell.com/page/L7139X1ZEG.jpg)

Thank you for your time
Have a nice product development


# Page. 14

![Page Image](https://bcdn.docswell.com/page/G7WPQN86E2.jpg)

Appendix


# Page. 15

![Page Image](https://bcdn.docswell.com/page/4JZKW38RJ3.jpg)

Climate for Learning


# Page. 16

![Page Image](https://bcdn.docswell.com/page/YE6QGXP1EV.jpg)

Code Maintainability
is the ease with which a codebase can be modified, understood, and extended
benefits:
Faster onboarding of new team
members
Reduced cognitive load
Lower defect rates
Quicker feature delivery
how to improve:
Clear code ownership
Consistent coding practices
Modular architecture
Automated code quality checks
Regular refactoring
Keeping dependencies up to date


# Page. 17

![Page Image](https://bcdn.docswell.com/page/GE5RVXKLJ4.jpg)

Documentation Quality
refers to having clear, up-to-date, and accessible documentation for code, processes, and
systems that helps teams work effectively and maintain knowledge
benefits:
Drives implementation of all technical
practices
Reduces time spent answering repetitive
questions
Better collaboration between teams
Emcorage more knowledge sharing
how to improve:
Focus on clarity, findability, and reliability
Establish documentation guidelines
Engage technical writers and
documentation champions
Provide technical writing training
Maintain active documentation practices


# Page. 18

![Page Image](https://bcdn.docswell.com/page/972D3XW37R.jpg)

Empowering Teams To Choose Tools
refers to giving teams the autonomy to select and use tools that best fit their needs while
maintaining necessary governance and security standards
benefits:
Increased productivity and job
satisfaction
Better tool adoption and utilization
Faster problem-solving
Enhanced innovation and
experimentation
Improved team ownership
how to improve:
Define clear governance boundaries
Create tool selection frameworks
Establish security and compliance
guidelines
Support experimentation periods
Provide resources for tool evaluation
Foster knowledge sharing about tools


# Page. 19

![Page Image](https://bcdn.docswell.com/page/DJY218L8JM.jpg)

Generative Culture
is one of the typologies of organizational cultures in &quot;A typology of organisation culture”
benefits:
Foster information flow
Better trust among people and
organizations
Enhanced psychological safety
Better problem-solving capabilities
how to improve:
Foster high cooperation across teams
Train messengers and welcome bad
news and negative feedback
Share risks and responsibilities
Encourage cross-functional bridging
Encourage learning from failures
Implement and reward novelty
Hold blameless postmortems


# Page. 20

![Page Image](https://bcdn.docswell.com/page/V7N82Q49E8.jpg)

Fast Flow


# Page. 21

![Page Image](https://bcdn.docswell.com/page/YJ9K1DQ3J3.jpg)

Continuous Delivery
is a principle and a practice to release changes of all kinds on demand quickly, safely, and
sustainably.
benefits:
Faster time to market
Reduce software risk
Improve customer satisfaction
Increase agility
Lower burnout
how to improve:
Implement automated testing
Establish deployment automation
Practice trunk-based development
Streamline deployment processes
Use infrastructure as code
Implement feature flags
Establish a rollback mechanism


# Page. 22

![Page Image](https://bcdn.docswell.com/page/GJ8R43GL7D.jpg)

Database Change Management
is the practice to make database changes consistent, reliable, and easy to maintain.
benefits:
Faster and safer database deployments
Reduce unscheduled downtime
Better collaboration between teams
Improve visibility into database changes
Ability to roll back changes safely
how to improve:
Store database changes as scripts in
version control
Use database migration tools and
frameworks
Implement zero-downtime deployment
strategies
Test changes against production-like
data


# Page. 23

![Page Image](https://bcdn.docswell.com/page/LJLK6VGQ7R.jpg)

Deployment Automation
is the practice of automating the process of deploying software to testing and production
environments with minimal manual intervention.
benefits:
Reduce deployment risks
Faster feedback on software quality
Consistent and repeatable deployments
Reduce manual errors
Improve deployment reliability
Faster time to market
how to improve:
Use the same deployment process for all
environments
Automate environment configuration
Implement deployment testing
Decouple deployments between
services
Design for automation from the start


# Page. 24

![Page Image](https://bcdn.docswell.com/page/47M25GLK7W.jpg)

Flexible Infrastructure
is the ability to provision and manage computing resources on-demand with cloud-native
practices.
benefits:
Faster throughput and higher stability
Better service availability
Enhanced cost visibility and control
Faster environment provisioning
Greater scalability and elasticity
Better resource utilization
how to improve:
Implement infrastructure as code
Enable self-service provisioning
Adopt cloud-native architectures
Use automated configuration
management
Establish proper cost monitoring
Implement SRE practices


# Page. 25

![Page Image](https://bcdn.docswell.com/page/P7RM3ZK6J9.jpg)

Loosely Coupled Teams
is the ability of teams to work independently and make changes without requiring
extensive coordination with other teams.
benefits:
Higher developer productivity
Faster and safer deployments
Increased team autonomy
Better deployment outcomes
Improved job satisfaction
More experimentation opportunities
how to improve:
Build cross-functional teams
Define clear service contracts
Implement service-oriented architecture
Enable independent testing and
deployment
Use versioned APIs


# Page. 26

![Page Image](https://bcdn.docswell.com/page/PJXV49LDEX.jpg)

Streamlining Change Approval
is the practice of optimizing change management processes to enable fast and safe
software delivery while maintaining necessary controls and compliance.
benefits:
Faster time to production
Reduced deployment risks
Better compliance management
Increased team autonomy
Higher software delivery performance
More efficient resource utilization
how to improve:
Implement peer review processes
Use automated testing &amp; validation
Move approvals closer to development
Establish risk-based approval paths
Automate security &amp; compliance checks
Focus on clear process communication


# Page. 27

![Page Image](https://bcdn.docswell.com/page/3JKQZPLDJD.jpg)

Version Control
is a system to track and manage changes to code, configurations, and other software
development artifacts in a controlled and organized way.
benefits:
Reproducibility of environments
Traceability of changes
Disaster recovery capability
Better auditability
Quick response to defects
how to improve:
Store all code and dependencies
Version all configuration files
Include infrastructure code
Maintain build and deployment scripts
Keep test scripts and documentation


# Page. 28

![Page Image](https://bcdn.docswell.com/page/LE3PDX3PJ5.jpg)

Working in Small Batches
is a principle and practice of breaking down work into smaller, manageable pieces that can
be completed independently and in short timeframes.
benefits:
Faster feedback on changes
Easier problem fixes
Increased efficiency
Increased motivation with small wins
Prevents sunk-cost fallacy
Enables rapid learning and validation
how to improve:
Break features into independent units
Make changes negotiable and iterative
Keep work small and estimable
Ensure changes are testable
Use feature toggles and dark launches
Small and short projects


# Page. 29

![Page Image](https://bcdn.docswell.com/page/8EDLP243JG.jpg)

Fast Feedback


# Page. 30

![Page Image](https://bcdn.docswell.com/page/V7P2N1MP78.jpg)

Continuous Integration
is a practice of frequently integrating code changes into a shared repository, with
automated builds and tests to detect problems early.
benefits:
Faster feedback loops
Higher deployment frequency
More stable systems
Higher quality software
Reduced integration problems
Better team coordination
how to improve:
Automate build process
Create comprehensive test suites
Fix broken builds immediately
Keep test execution time short
Merge to trunk at least daily
Use automated notifications


# Page. 31

![Page Image](https://bcdn.docswell.com/page/2JVDKY9VJQ.jpg)

Monitoring and Observability
enable the practice of using tools and technical solutions to watch, understand, and
actively debug systems.
benefits:
Faster incident detection
Reduced time to restore service
Better system understanding
Improved debugging capabilities
Data-driven decision making
Enhanced system reliability
how to improve:
Implement comprehensive system
health monitoring
Track customer-facing metrics
Implement metrics, logs, and traces
Create symptom-based alerts
Keep appropriate alerts


# Page. 32

![Page Image](https://bcdn.docswell.com/page/5EGYQ9Z1EL.jpg)

Resilience Engineering
is the practice of designing and operating systems that can withstand and recover from
failures.
benefits:
Higher system availability
Reduced downtime
Better user experience
Enhanced system reliability
Improved team morale
how to improve:
Implement redundancy and failover
mechanisms
Use automated monitoring and alerting
Test recovery procedures
Foster a culture of learning from failures


# Page. 33

![Page Image](https://bcdn.docswell.com/page/4JQMKWLN7P.jpg)

Pervasive security
is the practice of integrating security into all aspects of software development and
operations.
benefits:
Reduced security risks
Improved system security
Enhanced user trust
Better compliance
Reduced operational costs
how to improve:
Integrate security into all phases of the
software development lifecycle
Use automated security tools
Foster a culture of security awareness
Implement secure coding practices
Regularly review and update security
policies


# Page. 34

![Page Image](https://bcdn.docswell.com/page/K74VPKD3J1.jpg)

Test Automation
is the practice of continuously running automated tests throughout the software delivery
lifecycle to validate functionality and get fast feedback on changes.
benefits:
Faster feedback cycles for developers
Improved software stability
Lower deployment pain
More reliable testing compared to
manual
Helps developers learn to write testable
code
how to improve:
Continuously curate and improve test
suites
Build acceptance tests for key user
journeys
Integrate tests into CI/CD pipelines
Pair testers with developers


# Page. 35

![Page Image](https://bcdn.docswell.com/page/LJ139XZZ7G.jpg)

Test Data Management
is the practice of managing data used in testing to ensure tests can validate realistic
scenarios while maintaining security and efficiency.
benefits:
Enables comprehensive test validation
Supports realistic testing scenarios
Helps reproduce defects effectively
Allows testing edge cases
Improves test reliability
Reduces maintenance costs
how to improve:
Make adequate test data readily
available in automated testing
Minimize reliance on test data
Isolate test data environments
Regularly refresh and maintain test data
Mask sensitive production data


