What are good KPIs for a dev team?So some of the bad KPIs, like lines of code, are easy to detect. But how do we choose a good KPI?
“What are some good KPIs we can use to measure my dev team?” someone recently asked me.
What do you think?
Some metrics are obviously bad. Lines of code produced, for example. Or number of PRs merged. Even number of story points completed.
So some of the bad KPIs are easy to detect.
But how do we choose a good KPI?
I don’t know.
And neither do you.
How can I be so sure?
Because neither you, nor I, nor the question asker, knows what the goals of the team are.
KPIs don’t exist in a vacuum. KPIs are key indicators of progress toward an objective (aka an OKR).
So actually, maybe lines of code is a good KPI. If the OKR is to double the lines of code.
If we don't use story points, how do we measure team effectiveness?
With respect to Goodhart's law, the DORA metrics are a place to start.
What are the common agile metrics people use?
This may seem like a perfectly reasonable question on its face. But is it? I see two problems here.
Introducing DORA the DevOps Engineer
How does your team do on these 4 key metrics identified as indicators of a highly-performing software team?
Improve your software delivery