Defining and Tracking Developer Productivity Metrics

21min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

In this chapter, they discuss the process of defining and tracking developer productivity metrics. They talk about how different organizations define teams within their organization and the challenges of consolidating a working definition. They also explore the top-down and bottom-up approaches to developing metrics and the importance of engaging with developers early on to determine the most meaningful measurements.

In this episode, Abi chats with Grant Jenks, Senior Staff SWE, Engineering Insights @ LinkedIn. They dive into LinkedIn's developer insights platform, iHub, and its backstory. The conversation covers qualitative versus quantitative metrics, sharing concerns about these terms and exploring their correlation. The episode wraps up with technical topics like winsorized means, thoughts on composite scores, and ways AI can benefit developer productivity teams.

(1:10) Insights in the productivity space
(7:13) LinkedIn's metrics platform, iHub
(12:52) Making metrics actionable
(15:35) Choosing the right and wrong metrics
(19:39) The difficulty of answering simple questions
(26:23) Top-down vs. bottom-up approach to metrics
(32:12) Winsorized mean and selecting measurements
(39:25) Using composite metrics
(46:57) Using AI in developer productivity