Download as PDF, PPTX
Uploaded byProjectCon
Ryan Ripley - The #NoEstimatesMovement
The document discusses the #NoEstimates movement in software development, which explores alternatives to traditional estimation practices. It notes that estimates often do not directly add value and the movement aims to reduce reliance on estimates or stop using them where possible. Key ideas include using story points instead of hours, limiting story sizes, and building cumulative flow diagrams to make decisions without estimates. The goal is to improve workflows so that estimates become unnecessary.
More Related Content
Similar to Ryan Ripley - The #NoEstimatesMovement
Ryan Ripley - The #NoEstimatesMovement
- 1.
- 2.
- 7. We are uncoveringbetter ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
- 8. Stacey Diagram • Simple:Everything is known • Complicated: More is known than unknown • Complex: More is unknown than know • Chaotic: Very little is known
- 9.
- 10.
- 11.
- 12.
- 13.
- 14. Dictionary.com - anapproximate judgment or calculation, as of the value, amount, time, size, or weight of something. Merriam-Webster - a : to judge tentatively or approximately the value, worth, or significance of b : to determine roughly the size, extent, or nature of c : to produce a statement of the approximate cost of The American Heritage Dictionary – 1. A tentative evaluation or rough calculation. 2. A preliminary calculation of the cost of a project. 3. A judgement based upon one’s impressions; opinion. Predicting the Unpredictable by Johanna Rothman – Literally, “guess.” How long or how much you think the project will take for date and/or cost. Software Estimation by Steve McConnell – A good estimate is an estimate that provides a clear enough view of the project reality to allow the project leadership to make good decisions about how to control the project and hit its targets.
- 15. EFFORT/COST/ DURATION OF THE WORK • Domain Knowledge • Programming Experience ACCIDENTAL COMPLICATION • Code Complexity • Design Decisions • Team Stability • Multitasking • Dependencies • Technical Debt • Legacy Code • Deployment Pipeline • Size of Your Stories • Clarity of Work • Quality of Requirements • Lack of Priorities • WIP Limits Too High • Management Discipline • Technology / Platform Changes • Team Collaboration • Craftsmanship ESSENTIAL COMPLICATION • Inherent Difficulty of the Work • Natural Disasters • Unforeseen Occurrences ESTIMATE =
- 16. ESTIMATE = “THEWORK” + “BUFFER”
- 17.
- 18. MAGIC NUMBERS “MULTIPLY BY2 AND ADD 2 WEEKS” 80% CONFIDENCE INTERVAL 1) MAKE YOUR ESTIMATES 2) ADD ONE 3) TAKE THE NEXT UNIT PAD THE NUMBERS BY 20% (WHY NOT 40%?) EXCEL GYMNASTICS
- 19. “IN 1986, PROFS.S.D. CONTE, H.E. DUNSMORE, AND V.Y. SHEN PROPOSED THAT A GOOD ESTIMATION APPROACH SHOULD PROVIDE ESTIMATES THAT ARE WITHIN 25% OF THE ACTUAL RESULTS 75% OF THE TIME.” SOURCE: Software Estimation by Steve McConnell
- 20. “OF THE LARGESYSTEMS THAT ARE COMPLETED, 66% EXPERIENCE SCHEDULE DELAYS AND COST OVERRUN.” SOURCE: Project Management Tools and Software Failures and Successes by Capers Jones – Journal of Defense Software Engineering
- 21. 80% of ProjectsAre Late or Failed **Cost and/or duration estimates not met. SOURCE: Software Estimation by Steve McConnell Overall, a compelling number of studies have found results in line with the results reported by The Standish Group and Jones, that about one quarter of all projects are delivered on time; about one quarter are cancelled; and about half are delivered late, over budget, or both.
- 22. “17% OF LARGEIT PROJECTS GO SO BADLY THAT THEY CAN THREATEN THE VERY EXISTENCE OF THE COMPANY.” SOURCE: McKinsey & Company with University of Oxford – Study on large scale IT projects - 2012
- 23.
- 24.
- 25.
- 26.
- 27. #NOESTIMATES IS AHASHTAG FOR THE TOPIC OF EXPLORING ALTERNATIVES TO ESTIMATES FOR MAKING DECISIONS IN SOFTWARE DEVELOPMENT. THAT IS, WAYS TO MAKE DECISIONS WITH “NO ESTIMATES”
- 28. THIS IS THEMAIN PREMISE BEHIND #NOESTIMATES: ESTIMATES DO NOT DIRECTLY ADD VALUE TO YOUR PROCESS, SO WE WANT TO FIND WAYS TO REDUCE THE ESTIMATION PROCESS OR EVEN STOP IT WHERE POSSIBLE
- 29. #NOESTIMATES ISN’T ABOUT DITCHINGESTIMATES. IT IS ABOUT IMPROVING THE WAY WE WORK SUCH THAT ESTIMATES BECOME REDUNDANT
- 34. “Bill Hanlon lookedat 60-ish projects that used relative estimates. He looked at how accurate their predictions were as compared to the actuals. Then he reset all estimates to 1 and recomputed their velocities, made accordant projections and compared those to actuals. He found about a 3% variance in predictive accuracy between full data and just using 1. SOURCE: Planning with Any Hope of Accuracy by Arlo Belshee - http://arlobelshee.com/planning-with-any-hope-of-accuracy/
- 49. NEXT STEPS: 1. IFYOU ESTIMATE IN HOURS MOVE TO SP’s 2. DON’T ESTIMATE TASKS 3. LIMIT THE SIZE OF STORIES 4. IF YOU USE SP’s, ONLY USE 1,3, and 5 5. BUILD CUMULATIVE FLOW DIAGRAMS 6. EVERY STORY CAN BE A 1 7. NEGOTIATE DECISIONS, NOT ESTIMATES
- 50. Recommended Resources: Blogs: • WoodyZuill - http://zuill.us/WoodyZuill/ • Neil Killick – http://neilkillick.wordpress.com/ • Vasco Duarte - http://oikosofy.com/news/ YouTube Videos: • Alan Holub’s #NoEstimates Keynote - https://www.youtube.com/watch?v=QVBlnCTu9Ms • Woody Zuill’s #NoEstimates: Lets Explore the Possibilities - https://www.youtube.com/watch?v=5oMk2oRJNbc Books: • Vasco Duarte’s #NoEstimates Book - http://noestimatesbook.com/ • Johanna Rothman’s Predicting the Unpredictable - http://amzn.to/2mG2qXd Podcasts: • Agile for Humans Episode 52 “Software Estimation with Steve McConnell” - http://ryanripley.com/afh-052-software-estimation-with-steve-mcconnell-podcast/ • Agile for Humans Episode 50 “Agile Ideas with Neil Killick” - http://ryanripley.com/afh-050-agile-ideas-with-neil-killick-podcast/ • Agile for Humans Episode 45 “System Thinking and #NoEstimates with Chris Chapman” - http://ryanripley.com/afh-045-system-thinking-and-noestimates-with-chris-chapman-podcast/ • Agile for Humans Episode 20 “#NoEstimates with Vasco Duarte” - http://ryanripley.com/noestimates-with-vasco-duarte/
- 51. PROFESSIONAL SCRUM MASTERII (PSM II) INDIANAPOLIS, IN OCTOBER 3-4, 2018 https://ryanripley.com/psm2indy USE THE CODE: SERVANTLEADER FOR $100 OFF THE COURSE
- 52.
- 53.