Estimates are one input that teams use to plan their sprints but can often be subjective, inaccurate, or based on unclear requirements. Building in time for teams to collaborate and discuss estimates is critical to achieving sprint goals consistently and there are several activities teams can employ. This presentation will provide examples of how Scrum teams can improve their estimates to achieve an optimal velocity and avoid burnout. An empirical approach to estimating work rather than a predictive one utilizes observations and evidence that inform future estimates. The empirical approach also encourages bottom-up estimates which seek to remove influence from management or other stakeholders.

Individuals often underestimate the time it takes to do something while overestimating their own abilities, which can lead many projects to fail. Time and effort estimates are hard, which is why Scrum measures work in units of complexity, or story points. During this session attendees will explore user story sizing and pointing techniques, Scrum metrics and reporting, and how to encourage t-shaped skills within their team. Other takeaways include an Estimate Health Checklist which attendees can use with their own team.