Engineering teams have two well-established frameworks for measuring performance: DORA and SPACE. Both are backed by serious research. Both are used by teams at scale. But they measure different things, and using the wrong one for the wrong question will give you misleading data.
DORA measures how fast and reliably software ships. SPACE metrics measure the full experience of developer work, including factors that never appear in a deployment log.
This guide explains what each framework tracks, where each falls short, and how to decide which to use, or whether to use both.
What Is DORA?
DORA (DevOps Research and Assessment) is a set of four metrics that measure software delivery performance. It was developed through the State of DevOps research program, now part of Google Cloud's DORA research team.
The four metrics are:
• Deployment frequency: How often code ships to production.
• Lead time for changes: How long from code commit to production deployment.
• Change failure rate: What percentage of deployments cause incidents or require rollback.
• Failed deployment recovery time: How long to restore service after an incident.
DORA classifies teams as Elite, High, Medium, or Low performers based on these metrics. Elite teams deploy multiple times per day with a lead time under one hour, a change failure rate below 5%, and a recovery time under one hour. Low performers deploy monthly and take a week or more to recover from failures.
The strength of DORA is precision. All four metrics are tied directly to deployment events, which means they can be measured objectively and tracked over time. If you want to know whether your team is improving at shipping software, DORA gives you a clear answer.
The limitation is that DORA only measures delivery. A team can hit Elite DORA numbers while engineers are burning out, the codebase is degrading, or collaborative practices are breaking down. DORA will not surface any of that.
For a deeper look at implementing DORA metrics and interpreting benchmark data, see our complete DORA metrics guide.
What Are SPACE Metrics?
SPACE is a developer productivity framework introduced by Nicole Forsgren, Margaret-Anne Storey, Chandra Maddila, Thomas Zimmermann, Brian Houck, and Jenna Butler in a 2021 paper published in ACM Queue. The framework covers five dimensions:
Satisfaction and well-being: How engineers feel about their work and whether their needs are met. Measured through surveys and sentiment data, not deployment systems.
Performance: The outcomes of the work: code quality, reliability, review impact. This dimension focuses on results, not volume.
Activity: What engineers do: commits, pull requests, code reviews, builds. The visible proxy for output, and the dimension most organizations over-index on.
Communication and collaboration: How teams coordinate, share knowledge, and integrate across functions. Particularly relevant in distributed or multi-team environments.
Efficiency and flow: Whether engineers can do focused work without interruption. Measured through handoff counts, wait times, and context-switching frequency.
SPACE was designed to address a specific problem: engineering organizations were measuring productivity through activity metrics alone, such as commits, story points, and lines of code. This approach creates perverse incentives and misses most of what actually determines whether a team is productive.
The key finding in the paper is that no single metric captures developer productivity. You need at least three to five dimensions, and no dimension should be used in isolation.
SPACE vs DORA: Key Differences
Both frameworks are backed by substantial research. DORA has over a decade of data across thousands of organizations. SPACE is newer but draws on a research tradition spanning Microsoft, GitHub, and academic computer science.
When to Use DORA
Use DORA when your question is specifically about delivery:
• Is the team shipping faster than six months ago?
• How does deployment frequency compare to industry benchmarks?
• Is the change failure rate trending up, and are incidents taking longer to resolve?
• How does delivery performance compare across teams?
DORA is also the right choice when you need objective, automated measurement. The four metrics can be pulled directly from your CI/CD pipeline and deployment systems. No surveys required.
Engineering teams in financial services, particularly those working under compliance and release governance requirements, use DORA as a baseline. Regulators increasingly treat deployment frequency and recovery time as indicators of engineering maturity.
When to Use SPACE Metrics
Use SPACE when your question goes beyond delivery:
• Is the team burning out, even though velocity looks fine on paper?
• Why is onboarding taking three months instead of six weeks?
• Are senior engineers spending most of their time in code review rather than design work?
• Does team satisfaction correlate with code quality trends?
SPACE is particularly useful after a team restructure, following a major incident, or when retention becomes a concern. If engineers are leaving and you do not know why, satisfaction and well-being data from the SPACE framework often surfaces the cause before attrition becomes visible in headcount data.
Using DORA and SPACE Together
Most engineering leaders do not have to choose between them. DORA and SPACE answer different questions. Running both gives you delivery performance data and developer experience data in the same reporting cycle.
A practical combination:
• Track DORA metrics continuously through your CI/CD tooling.
• Run a SPACE survey quarterly or after major organizational events.
• Cross-reference: when DORA metrics decline, does it coincide with a drop in satisfaction or a spike in interruptions?
This pattern turns two separate frameworks into a diagnostic system. A deployment frequency drop that coincides with a communication breakdown points to a coordination problem. The same drop alongside high well-being scores points to a tooling or process bottleneck, which calls for a different intervention.
For more on building a complete measurement system, see our engineering operations guide.
How Scrums.com Supports Both Frameworks
Scrums.com is an engineering intelligence platform that surfaces DORA metrics, SPACE dimensions, and sprint health data across your engineering teams in a single dashboard. It connects to Jira, GitHub, and your CI/CD pipeline automatically, so DORA data is available without manual logging. Quarterly SPACE survey templates are included. See how it works.
Frequently Asked Questions
What is the difference between SPACE metrics and DORA metrics?
DORA measures software delivery performance through four metrics: deployment frequency, lead time for changes, change failure rate, and failed deployment recovery time. SPACE metrics cover developer productivity across five dimensions: Satisfaction, Performance, Activity, Communication, and Efficiency. DORA focuses on delivery outcomes; SPACE captures the human and collaborative factors that determine sustained productivity.
Can you use SPACE and DORA at the same time?
Yes. DORA and SPACE answer different questions and work well in combination. DORA gives you objective delivery data from deployment systems. SPACE adds satisfaction, collaboration, and flow data, typically gathered through surveys. Engineering leaders who track both can cross-reference delivery performance against developer experience to diagnose root causes more accurately.
Is SPACE metrics or DORA better for engineering teams?
Neither is universally better. DORA is better for measuring delivery velocity and reliability, especially when benchmark comparisons matter. SPACE is better for understanding developer productivity in full, including well-being and collaboration. For most teams, using DORA as a continuous baseline and running SPACE quarterly is more useful than choosing one over the other.
What are the five SPACE dimensions?
The SPACE framework covers Satisfaction and well-being, Performance, Activity, Communication and collaboration, and Efficiency and flow. The framework was introduced by Forsgren et al. in a 2021 ACM Queue paper and is designed to be used with multiple dimensions together, not as isolated metrics.
What are the DORA benchmark tiers?
DORA classifies teams as Elite, High, Medium, or Low performers. Elite teams deploy multiple times per day, have a lead time under one hour, a change failure rate below 5%, and a recovery time under one hour. The DORA State of DevOps Report, published annually by Google Cloud's DORA team, is the primary source for current benchmark data.
