Whitepaper Review: Measuring Developer Goals (Category Management)

I read it the other day. story Google kids coming out in the fall 2024 A year that focused on measuring how software engineers achieve their work goals:) Ciera Jaspan and Collin Green (two Google leads) Understanding and effectively measuring goals is critical to improving the developer experience and improving their effectiveness. This article is a follow-up to the first article, “A Human-Centered Approach to Developer Productivity,” about which I am referring. told A year ago. In general, the topic is relevant to me, so I decided to write a review on it.

It all starts with the fact that often you need answers to questions of the species.

How often do developers have to drop a test? How long does it take for a developer to set up a new server? How many developers use a specific tool to check code quality? Have we really improved the way developers do their work?

And to answer such questions, it is more convenient to tie measurements not to specific tools, but to the goals that developers set themselves when using tools. This allows you to answer questions similar to those above, keeping metrics user-centric rather than a tool. The bottom line is that engineers have to use a lot of tools to do their job, and we have to design measurements so that they are not limited by the boundaries of specific tools.

Next, the guys describe their approach to formulating a list of 30 objectives that cover the entire SDLC (software development lifecycle)The implementation of which can be tracked by tool logs, as well as by a quarterly survey of engineers’ satisfaction.

And what the guys get as a result of this approach can be read in my review:)

#Management #Leadership #Software #SoftwareDevelopment #Architecture #SoftwareArchitecture #Metrics #Devops #Processes