If we don't use story points, how do we measure team effectiveness?

July 12, 2022
With respect to Goodhart's law, the DORA metrics are a place to start.

As a follow-up to yesterday’s reader question, I was asked:

Do you use any metrics to work out how effectively the team are delivering?

Of course, with all due respect to Goodhart’s law, the DORA metrics are often a good place to start:

  • Deployment Frequency — How often an organization successfully releases to production
  • Lead Time for Changes — The amount of time it takes a commit to get into production
  • Change Failure Rate — The percentage of deployments causing a failure in production
  • Time to Restore Service — How long it takes an organization to recover from a failure in production

However, you don’t necissarily need to even measure these metrics for them to be a useful guide, as Dave Mangot discussed with us on the most recent episode of the Adventures in DevOps podcast, DevOps Research and Assessment (DORA) Metrics with Dave Mangot.

Share this

Related Content

Introducing DORA the DevOps Engineer

How does your team do on these 4 key metrics identified as indicators of a highly-performing software team?

Velocity, capacity, and unplanned work

Velocity usually includes unplanned work, which limits its usefulness for capacity planning and forecasting.

Reader question: Alternatives to Story Points for Sprint planning

My opinion is that days are usually better than story points, for the simple reason that they're less confusing.