Engineering Delivery Metrics (DORA)

Agreed definitions, traceable deploy and incident data, a trustworthy baseline for the four DORA metrics, review rhythms and the experiments that improve delivery without anyone gaming the numbers.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Engineering Delivery Metrics (DORA), and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Engineering Delivery Metrics (DORA)

Measuring deployment frequency, lead time, change failure rate and recovery time to improve delivery without gaming the numbers.

  1. Written purpose for measuring delivery
  2. Shared definitions of the four DORA metrics
  3. Inventory of delivery data sources
  4. What counts as a production deployment
  5. Traceability from commit to deploy
  6. Linking incidents and rollbacks to changes
  7. Ninety-day DORA baseline for one team
  8. Choosing the unit you report on
  9. Team agreement on how metrics are used
  10. Build or buy a delivery metrics tool
  11. Delivery numbers in the weekly retro
  12. Monthly delivery review with engineering leads
  13. Delivery data quality audit
  14. Quarterly delivery trend report
  15. Weekly change failure classification
  16. Lead time stage breakdown
  17. Deploy log annotations and hygiene
  18. Metrics dashboard ownership and upkeep
  19. Counter-metrics and gaming watch
  20. Improvement experiment backlog
  21. Reading the research behind DORA
  22. Percentiles and distributions for lead time
  23. Process behaviour charts for delivery data
  24. Value stream mapping skills
  25. SPACE and developer experience signals
  26. Flow metrics alongside DORA
  27. Querying the delivery events store
  28. Explaining delivery metrics to non-engineers
  29. Smaller pull requests to cut lead time
  30. Cutting time to first review
  31. Lowering change failure rate at the top cause
  32. Shorter time to restore service
  33. Separating deploy from release with flags
  34. Setting targets from benchmark tiers or trend
  35. Adding reliability as a fifth metric
  36. Retiring vanity delivery metrics
  37. Value stream mapping workshop for one product
  38. Yearly delivery review and target reset
  39. Launching delivery metrics to the engineering org
  40. Re-baselining after a reorganisation
  41. Developer experience survey beside DORA
  42. Delivery metrics for a single startup team
  43. Enterprise rollout across many teams
  44. Delivery metrics under change approval rules
  45. New manager inheriting a team's metrics
  46. Engineer's case for fixing the delivery pipeline
  47. Adapting DORA for mobile and release trains
  48. Causal analysis of delivery improvements
  49. Delivery metrics for a platform team
  50. Event-based delivery metrics pipeline

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Written purpose for measuring delivery

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Teams that start collecting DORA numbers without saying why usually end up with a leaderboard nobody trusts.

First tasks

  • Write down the three questions you most want delivery data to answer
  • List the uses of the metrics that the team will not accept
  • Share the draft purpose page with two engineers for comments
  • Publish the agreed page next to where the dashboard will live

Shared definitions of the four DORA metrics

Ask five engineers when lead time starts and you will get first commit, pull request opened and ticket created. Without one written definition per metric, including start and end events, what counts as a failure and what counts as restored, two teams can report the same week with numbers that cannot be compared. These definitions become the contract every later dashboard is built against.

First tasks

  • Ask three engineers when they think lead time starts and note the answers
  • Draft start and end events for each of the four metrics
  • List the change types that count as a failure, such as rollback, hotfix or incident
  • Commit the definitions file to the team repository with a named owner

Inventory of delivery data sources

Delivery data is scattered across the version control host, the CI system, the deploy tool, the incident tracker and sometimes a change ticketing system. Mapping which system records which event, how long it keeps history and how you can get at it shows early whether a metric is cheap to compute or needs new instrumentation. Do it before buying or building anything.

First tasks

  • List every tool that touches a change between commit and production
  • Check how many months of history each tool keeps and how to export it
  • Mark which metric each tool's events can support
  • Write the gaps that need new instrumentation at the bottom of the table

Make it yours.

Install Engineering Delivery Metrics (DORA), then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.