Soft Skills Engineering

In this episode, Dave and Jamison answer these questions: I’m a manager on a Product team. I’ve been asked by upper management to measure “story points completed per developer per sprint” and display the results publicly each sprint to motivate lower-performing employees. I explained why, according to Scrum, I don’t think this is a good idea. But I think my explanations came across as me not wanting to make my team accountable for performance. For some context, I currently track productivity by reading daily updates, PRs, and tickets, from each developer. I worry that “story points” is easily game-able as a performance target, and will make the team want to modify the points after the fact to reflect actual time spent. Then story points will become a less useful tool for project planning. I’d like to satisfy the higher-up ask to measure productivity, but in a way that is good for the team, the company, and my career. Any thoughts on how to approach this? A listener named