It happens to all of us. You have built your backlog, the tasks are all in order, everyone is committed to the work. Everyone feels great about a backlog well planned and is ready to get to work. And then someone does it, they use the ‘E’ word. “What is our estimate for this?”. A chorus of groans breaks out. Suddenly, two developers come to fisticuffs over the difference between a 2-point and a 3-point story. The SDET storms out because we haven’t included enough time for testing. The Product Owner climbs on the table to start preaching the difference between accuracy and precision. Join this season and learn how to avoid this scene, or the groan factor, at your next planning without giving up the value of estimates. In this session we will learn:
• Why “the business” wants estimates and how to make sure they aren’t abused
• Why the development team should want estimates and how to reduce the trauma
• Using estimates now to avoid disappointment and overtime later
• Accuracy vs Precision, Story points vs t-shirt sizes, and all the ways we do this wrong
• When to estimate, who to estimate with, and how to keep it all for being a lie