Software estimates are everywhere, yet they are often misunderstood, misused, or treated as commitments rather than forecasts. In this session, we will explore why teams estimate, what they are really estimating, and why translating “complexity” into time can be so problematic.

Drawing from past experiences, this presentation looks at common estimation approaches such as Planning Poker, story points, as well as practical best practices. We will also discuss how teams can try to improve their estimation skills over time.

Whether you are a developer, product owner, or manager, this talk will help you better understand the purpose of estimates, their limitations, and how to make them more meaningful and useful for your team.