Goldilocks doesn't need your story points. or your t-shirts
summary
Claim: stop wrestling over Fibonacci numbers and t-shirt sizes and instead make work just right size then measure outcomes. Teams ask if a task is small enough if not break it down, or do more Discovery first. The concrete metric offered is tasks per person per week and showing that a steady average — with outliers discussed in retros — yields predictable delivery without mapping points to time. Examples and simple rules for when to split work are given.
AI-written summary · about
related talks
51mLearn how to improve velocity, predictability & agility
30mHow to Visualize Impacts to Your Workflow & Metrics
47mBe Ready, Be Done: The Art of Slicing User Stories
44mInspect & Adapt, then What?
35mCracking the WIP
33mTaming The Chaos: After The Quick Wins
30mTaming the Chaos: Beyond the Quick Wins
47mThe Only 2 Things needed to Scale Agile