Subscribe to our 0800-DEVOPS Newsletter

    Get in touch

    Not sure where to start? Let our experts guide you. Send us your query through this contact form.

      Get in touch

      Contact us for all inquiries regarding services and general information

        Use the form below to apply for course

          Get in touch

          Contact us for all inquiries regarding services and general information

          0800-DEVOPS #53

          Measuring developer productivity with Bryan Finster

          clock6 minute read

          A newsletter that started as a personal learning and getting-in-touch project by Ivan Krnic grew into a sociotechnical newsletter covering topics of technical excellence, organizational improvements, and productivity.

          Developer productivity

          Charity Majors once said:

          ✨ “Great engineers don’t make great teams. Great teams make great engineers.”

          In the age of complexity, teams are what build software. Teams deliver!

          That’s why a recent shortsighted McKinsey report suggesting measuring and comparing individual developer productivity on questionable criteria fell hard on many software development leaders. Turning software development from a team sport back to an individual game brings heroes and rockstar developers back onstage. Incentives based on individual achievements create “every man for himself” dynamics – collecting points is more important than delivering value to end users.

          Gene Kim often quotes Brian Eno, who coined the word “scenius” – the intelligence of a whole operation or group of people, as opposed to a traditional individual “genius.” Scenius > Genius anytime.

          There is a reason why software engineering leaders are stepping up and warning about the approach laid out in the report. It goes against many things we’ve painfully learned as an industry in the last 20-30 years.

          The McKinsey report is dragging software development back to Taylorism, and we shouldn’t let that happen. I talked about it with Bryan Finster.

          Interview of the Month

          Developer productivity with Bryan Finster

          Developer productivity with Bryan Finster

          Bryan Finster is a Distinguished Engineer at Defense Unicorns and a relentless searcher for better ways of working – not by following prescribed frameworks but by gaining situational awareness and recognizing specific contextual improvements. We discussed a topic that stirred an otherwise dull summer – McKinsey’s report on measuring developer productivity.

          DevOps Quiz

          Mini quiz

          What do you say?

          My company measures developer productivity

          DevOps Quiz

          Hand picked

          My Response To The NONSENSE McKinsey Article On Developer ProductivityDave Farley shares his thoughts on the implications of measuring individual developer productivity and what such metrics will lead to.

          Measuring developer productivity – Since McKinsey report compares software development with sales and HR, Steve Fenton points out that “while other functions can be measured reasonably well, some even with just a single metric, in software development, the link between inputs and outputs is considerably less clear.”

          5 Minute DevOps: McKinsey Gets Developer Productivity Wrong – Further thoughts on measuring developer productivity by Bryan Finster.

          Measuring goalposts – when measuring, people like to jump straight into reading the numbers but often forget why, what, and how they are measuring. William Bartlett takes us back to basics.

          Read with us

          Read with us

          Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations

          link Get the book

          Given the topic, it is only appropriate to go back and reread the Accelerate and the science behind achieving organizational productivity.

          Header photo by K8 on Unsplash

          DevOps articles delivered monthly.

          Ivan Krnić

          Ivan is Director of Engineering at CROZ, curator of 0800-DEVOPS newsletter, podcast host and O'Reilly author contributing to "97 Things Every Cloud Engineer Should Know". His special areas of interest cover DevOps culture, sociotechnical nature of software delivery and cloud native architectures. Particularly interested in leadership and organizational change, he is helping organizations align business and tech, focus their efforts, and essentially work smarter, not harder. You can follow him on Twitter as @ikrnic.

            DevOps articles delivered monthly.