Agile for Humans with Ryan Ripley and Todd Miller

YDS: Do Scrum Teams Track Individual Story Points?

6 snips
Mar 10, 2023
Tracking individual story points in Scrum teams can lead to unhealthy competition and disrupt teamwork dynamics according to Todd and Ryan. They believe it is a reckless metric that can impact behavior negatively and pit teammates against each other. The podcast discusses how this practice hides things and provokes behaviors that go against collaboration.
Ask episode
AI Snips
Chapters
Transcript
Episode notes
ADVICE

Don't Track Individual Story Points

  • Avoid tracking individual story-point totals for developers because it damages teamwork and skews behavior.
  • Do measure team outcomes and collaboration instead of individual velocity to preserve cooperative incentives.
ADVICE

Resist Per-Person Point-Based Reviews

  • Avoid using story points as a basis for individual performance reviews because the metric is arbitrary and reckless.
  • Do resist management pressure to implement per-person point tracking and defend team-focused measures.
INSIGHT

Individual Velocity Hides True Work

  • Measuring individual velocity gives a false and incomplete picture of contribution and hides important context.
  • It incentivizes avoiding help, bugs, and production work because those lower visible numbers.
Get the Snipd Podcast app to discover more snips from this episode
Get the app