#NoEstimates is an approach to software development that arose from the observation that large amounts of time were spent over the years in estimating and improving those estimates, but we see no value from that investment. Indeed, according to scholars Conte, Dunmore and Shens [1] a good estimate is one that is within 25% of the actual cost, 75% of the time.

This is the same as saying: give us your money, we promise not lose more than 25% of it (with a 25% probability that we will lose a lot more). We don’t find that acceptable or productive for our industry. There must be better ways to manage software and product development.

In this workshop we will review and analyze why we do estimates and how we can improve software and product development while reducing the time and money invested in estimating.

[1] Paper referred to by Steve McConnell in his book: Software Estimation, Demystifying the Black Art

• Decision making frameworks for projects that do not require estimates

• Investment models for software projects that do not require estimates

• Project management (risk management, scope management, progress reporting, etc.) approaches that do not require estimates

• The tools and arguments you need to prove the value of #NoEstimates to your boss

• How to get started applying #NoEstimates right away

• Where is #NoEstimates going and what are the likely changes to software development that will come next.

• Product Owners

• Team leaders

• Team members

• Agile Coaches

• Scrum Masters