Creating efficient, accurate, software estimations

Estimating projects is hard. Whether it’s negotiating technical debt, understanding new requirements, or grappling with a lack of useful documents; the number of moving variables make it difficult to judge just how long a project will really take. 

So how do we reckon with estimations? Do we try to get a deeper understanding of the task, account for overpromising, and try to story map a project? Or are estimations too much hassle for the value they provide?

In this session we’ll hear from both sides of the estimates/no estimates debate, dive into the problems that are currently apparent, and try to begin a journey to more accurate estimations.