The podcast discusses the challenges of measuring developer productivity in software development, emphasizing the importance of tailoring the message to different organizational levels. The speakers explore the difference between measuring outputs and outcomes, highlighting the importance of the enabling environment and individual performance. They also discuss the space framework for measuring metrics, expressing concerns about potential misuse. The episode concludes with gratitude to guests and listeners, promoting leaving reviews and subscribing.
51:01
forum Ask episode
web_stories AI Snips
view_agenda Chapters
auto_awesome Transcript
info_circle Episode notes
insights INSIGHT
Measurement Needs Nuance
McKinsey argued that you can measure developer productivity, provoking strong reactions from practitioners.
The panel emphasised nuance: measurement is possible but risky without context and care.
volunteer_activism ADVICE
Begin With Business Problems
Start by asking leaders what business problems they actually need to solve before picking metrics.
Use metrics to answer those problems, not to satisfy curiosity or vanity.
insights INSIGHT
Metrics Vary By Organizational Layer
Different organizational layers view productivity differently and require different metrics.
Tailor measures and messaging to executives, middle management, and teams separately.
Get the Snipd Podcast app to discover more snips from this episode
This week host Sam Hogarth convened a panel to discuss the recent McKinsey piece on measuring software developer productivity. It this typical consultant speak, or is there something to be said about this argument? Listen in and find out! Enjoy! Resources referenced in the discussion: McKinsey - Yes, you can measure software developer productivity Gergely Orosz & Kent Beck - Measuring developer productivity? A response to McKinsey (Pt 1) Gergely Orosz & Kent Beck - Measuring developer productivity? A response to McKinsey (Pt 2 - Gergely's Version) Gergely Orosz & Kent Beck - Measuring developer productivity? A response to McKinsey (Pt 2 - Kent's Version) Kent's LinkedIn posts "Absurd and naive" "ignored whether the patient got better." Align incentives, encourage relationships, shorten & sharpen feedback loops DORA SPACE Vitaly Gordon - McKinsey is talking about developer productivity and that's a good thing Dave Farley's response Dan Terhost-North - The Worst Programmer I Know Charity Majors - Can Engineering Productivity Be Measured? Nicole Forsgren - How to measure and improve developer productivity *** If you enjoyed this episode, please give us a review, a rating, or leave comments on iTunes, Stitcher or your podcasting platform of choice. It really helps others find us. Much thanks to the artist Krebs from Machine Man Records who provided us our outro music free-of-charge! If you like what you heard, check out these links to find more music you might enjoy! If you'd like to join the discussion and share your stories, please jump into the fray at our Discord Server! We at the Agile Uprising are committed to being totally free. However, if you'd like to contribute and help us defray hosting and production costs we do have a Patreon. Who knows, you might even get some surprises in the mail!
Agile Uprising Podcast