How I explain estimation to non-technical stakeholders
Estimation can be confusing the frustrating for teams to explain to stakeholders. Often stakeholders just want outcomes and commitments to delivery dates. Learn how I explain what estimation is and how it works for agile teams. Using simple concepts and language, I will share with you one of the ways I communicate both sizing and estimating of work.
Outline/Structure of the Talk
Introduction
- Why we estimate
- Separating sizing from time
- How relative sizing works
- Converting to the lowest common size
- Do you need to estimate?
- Estimating velocity through sampling
- Using a burn-up chart to baseline performance
- Release cycles and delivery dates
Conclusion
Questions
Learning Outcome
This session will share simple ways to explain how a team can estimate it's work and what it means to stakeholders. Attendees will learn simple language to use to help others understand how estimation works and what to expect from an agile team.
Through the use of real experiences, the presenter will demonstrate one of several ways to both size and estimate work a team has story carded and prioritised.
Target Audience
Agile team members
Prerequisites for Attendees
no prerequisites
Links
Robin’s public presentation history
Agile Brisbane Meetup – Characteristics of High Performing Teams – 2018 https://www.slideshare.net/robinlmack/characteristics-of-a-high-performing-team
Agile Brisbane Meetup – Lean Start-up & MVP – 2015
https://www.slideshare.net/robinlmack/agile-brisbane-lean-startup-mvp-march-2015-46022289
YOW Brisbane – Session Host - 2014
IT Leadership Summit, Brisbane – Data Driven Innovation – 2014
https://www.slideshare.net/robinlmack/data-driven-innovation-103088812
iLabs Mentor – UQ start-up incubator - 2013
Continuous Innovation Network Conference (Rome, IT) – Agile Innovation in Large Corporations - 2012
PMOZ Conference (Melbourne, AU) – Agile Funding and Governance & session chair - 2012
