Dev Team Metrics That Matter
The truth is, no one really likes being measured, especially devs. But business leaders like looking at numbers, so they grab what’s easily available - # of code changes, agile velocity, individual developer metrics. These types of metrics are unbalanced, exclude context, and hurt engineering culture as a whole.
Measuring should start by answering the question “What is the most valuable outcome?”
Why? Because what you measure is what your team will produce. If you start measuring the number of code changes as a key performance metric, you are going to see coding time, PR size, and Cycle Time all increase.
Don’t fall into this trap.
In this keynote session I discuss which team level metrics are most significant, the outcomes they produce, and strategies that will help you avoid the mistakes I’ve already made.
Yishai Beeri likes to solve problems, and that's why he was so fascinated with programming when he first encountered Logo back in the 80s, where the possibilities seemed endless.He has made it a focus of his career to solve complex programming problems, both as a consultant and entrepreneur. In 2014 he joined the CTO office of a fast-moving cloud security startup, which later was acquired by a networking giant. At this startup he also met Ori Keren and Dan Lines, now co-founders of LinearB. He joined them shortly after the company was established, in order to get back to what he loves most about engineering, solving big challenges, and this time he is focusing on the world of dev team metrics and software delivery management.