Presented in Agile Singapore 2013 Conference
Agile promotes empiricism and change, yet many practitioners continue to scope out and estimate delivery times and costs for software products and projects.
Defenders of the art of estimation claim that we need to estimate software projects in order to answer common business and customer questions such as:
- Should we go ahead with this project? (go/no-go)
- How much will it cost? (bottomline)
- When will it be done? (predictability)
- Should we do project B instead of A? (prioritisation)
This session challenges participants to flip these questions on their heads and seek alternatives to estimation rituals. It covers the many risks inherent with an estimation culture and demonstrates real, practical alternatives, both at the portfolio and the sprint level.
Participants will get the following learning outcomes:
- How to reduce the uncertainty and risk inherent with popular estimation models and rituals
- How to determine the price for your customer without estimation rituals
- How to determine delivery dates and roadmaps without estimation rituals
- How to determine which projects to pursue without estimation rituals
- How to do Scrum or XP without estimation rituals
- When, if ever, is it appropriate to estimate software projects?