Facilitated By Ami T.
Master the art and science of Agile estimation. Learn why relative sizing works better than time-based estimates and how to use estimation to improve predictability.
Why Estimation in Agile is Different:
Traditional time-based estimates often fail because they assume too much certainty. Agile estimation embraces uncertainty and uses relative sizing and team collaboration to improve accuracy.
Story Points Explained:
• What story points are (and what they’re not)
• Why relative sizing is more accurate than time estimates
• Using the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21
• How story points account for complexity, effort, and uncertainty
• The relationship between story points and velocity
Planning Poker – The Gold Standard:
• How Planning Poker works step-by-step
• The power of independent estimation
• Discussing differences to drive understanding
• When to use Planning Poker vs. other techniques
• Facilitating effective Planning Poker sessions
Alternative Estimation Techniques:
• T-Shirt Sizing: XS, S, M, L, XL (for quick, high-level estimates)
• Affinity Estimation: Grouping similar-sized stories
• The Bucket System: For estimating large backlogs quickly
• No Estimates: When to consider this approach
Live Planning Poker Game:
• Participate in a real Planning Poker session
• Estimate user stories as a team
• Learn from the discussion and calibration process
• Experience why Planning Poker improves estimates
Understanding Velocity:
• What velocity is and how to calculate it
• Using historical velocity for forecasting
• Why velocity is unique to each team
• Avoiding common velocity mistakes
• Using velocity for Sprint Planning
Common Estimation Pitfalls:
• Treating story points as time commitments
• Comparing velocity across teams
• Pressure to increase velocity artificially
• Estimating too precisely
• Forgetting to re-estimate as understanding grows
Benefits of Attending This Session:
Participants will understand why Agile estimation works, confidently facilitate Planning Poker sessions, use velocity for realistic forecasting, and help their teams avoid common estimation mistakes. You’ll leave with practical techniques you can use in your next Sprint Planning.