This episode explores the challenges of measuring developer productivity and the pitfalls of using readily gameable metrics like story points. Against the backdrop of a listener's request to measure story points completed per developer, the hosts discuss the inherent flaws in such an approach, highlighting how it can lead to distorted performance evaluations and hinder project planning. More significantly, the discussion pivots to Goodhart's Law, emphasizing that when a metric becomes a target, it ceases to be a good measure. For instance, the hosts suggest focusing on team-level metrics like cycle time and bug resolution rate, which are less susceptible to manipulation and provide a more holistic view of team performance. In contrast to individual-level metrics, these team-level metrics foster a sense of shared responsibility and encourage collaborative problem-solving. The hosts also address the importance of regular, individual performance discussions with team members, ensuring transparency and addressing performance issues proactively. Ultimately, the episode underscores the need for managers to focus on the desired outcomes rather than solely relying on easily manipulated quantitative metrics, and to communicate effectively with upper management about performance management strategies.
