The DORA Framework (Four Keys)
by Nicole Forsgren • Partner at Microsoft Research at Microsoft Research (formerly GitHub, Google/DORA)
Nicole is a leading expert in developer productivity and DevOps, known for co-authoring the award-winning book 'Accelerate' and the State of DevOps Reports. She holds a PhD in Management Information Systems and has helped define industry standards for software delivery performance.
🎙️ Episode Context
Nicole Forsgren discusses the science behind measuring and improving developer productivity using frameworks like DORA and SPACE. She debunks the myth that speed compromises stability, explains why qualitative data from developers often beats system telemetry, and provides tactical advice for engineering leaders to align metrics with business goals.
Problem It Solves
Identifying how high-performing technology organizations balance speed and stability in software delivery.
Framework Overview
A widely adopted framework that uses four key metrics to classify engineering performance. It proves that high performers do not trade off speed for stability; they achieve both by reducing batch sizes and automating processes.
🧠 Framework Structure
Deployment Frequency: How often code ...
Lead Time for Changes: Time from code...
Mean Time to Restore (MTTR): Time to ...
Change Failure Rate: Percentage of ch...
When to Use
When you need to benchmark your engineering team's delivery performance or build a business case for DevOps investments (CI/CD, automation).
Common Mistakes
Believing that moving slower increases safety (the 'Change Freeze' fallacy); ignoring the cultural capabilities required to support these metrics.
Real World Example
Retail companies often perform better than other industries statistically because the 'retail apocalypse' forced them to adopt cloud bursting and rapid delivery to survive events like Black Friday.
Speed and stability move together... If you push changes less frequently, you will have more unstable systems.
— Nicole Forsgren