Estimates is the Holy Grail upon which projects thrive or perish. It is also high-risk, low-reward work that doesn’t get us any closer to DONE, can (and often does) gets us into trouble with the business, causes a big rush that leads to overtime, cutting corners and even team death marsh.
So we all want to know: can we estimate better?
In this talk I want to consider what causes our estimates go terribly wrong. We will talk about what we can improve, what we may just have to accept, and discuss ideas from other industries regarding working with estimates.
I am a software architect and developer, an Agile proponent, and a great believer in building valuable software that users will love to use. I build large back-end systems that require high-performance and high-reliability, and process vast amounts of data. I believe that successful software is created by strong teams, requires good engineering practices, and evolves in close collaboration with the users.