Download to read offline
More Related Content
Similar to #No estimates #smidig15 oslo
#No estimates #smidig15 oslo
- 1. âSVEN SCHNEE, @MRSNOW76, SVEN.SCHNEE@OIKOSOFY.COM #NoEstimates TheArt of Getting your Product Development back on Track Source: N@ncyN@nce, Some rights reserved
- 2.
- 3. sven.schnee@oikosofy.com SMS: +49172 835 4210 http://j.mp/NoEstimates-Book Get your Free Copy of the Book!
- 5. R E AS O N S F O R E S T I M A T I N G
- 6. INVESTMENT DECISIONS AND PRIORITISATION REASONS FORESTIMATING Source: epSos .de, some rights reserved
- 7. Source: VersionOne 9thState of Agile Survey
- 8. âą Investments andprojects are run by âhow long does it take, how much does it costâ âą Backlogs are prioritised by how long does it take, because itâs easier
- 9. RISK MITIGATION REASONS FORESTIMATING
- 10. âą Complex featuresnormally are riskier and take longer, estimation unveils complex features âą Most complex items should be prioritised high or highest, to avoid failing late âą if you donât know how long it takes, will you make that critical market window or that fixed date?
- 11. WE WA NTTO K NO W WHE N WE âRE DONE REASONS FOR ESTIMATING Source: Moyan Brenn, some rights reserved
- 13. ⹠Developers areWTF!?#⊠⹠Project managers are.. ⹠Middle managers want to make sure that senior management is happy with the progress ⹠Senior management needs to report to the investors
- 14. What we alreadyknow⊠source: thinboyfatter, some rights reserved
- 15. FEATURES FOR THE NEXT1 -3 MONTHS WHAT WE ALREADY KNOW
- 18. W H AT W E W E R E A B L E T O D O T H E L A S T 3 - 6 M O N T H S WHAT WE ALREADY KNOW
- 20. HOW MUCH MONEYWE CAN SPEND WHAT WE ALREADY KNOW
- 21. T H ER I G H T S L I C I N G I S T H E A R T O F # N O E S T I M A T E S
- 22. S T OR YF E A T U R EE P I CT H E M E AGILE BREAKDOWN OF THE WORK THE RIGHT SIZE WHEN YOU NEED IT
- 23. ONLY WHAT ISNEEDED NOW, NOT MORE AGILE BREAKDOWN OF THE WORK
- 24. DONâT FOCUS ONMORE THAN 2 -3 MONTHS AGILE BREAKDOWN OF THE WORK
- 25. A PROJECT GETS DELAYED ONEDAY AT A TIME THE RIGHT SLICING
- 26. THE ONLY REALMEASURE OF PROGRESS IS RUNNING TESTED SOFTWARE A PROJECT GETS DELAYED ONE DAY AT A TIME
- 27. HOW DO COMPANIESMEASURE THE âSUCCESSâ OF THEIR PROJECTS? A PROJECT GETS DELAYED ONE DAY AT A TIME
- 28. Source: VersionOne 9thState of Agile Survey
- 29. W H EN I S A N A G I L E I N I T I A T I V E C O N S I D E R E D S U C C E S S F U L ? A PROJECT GETS DELAYED ONE DAY AT A TIME
- 30. Source: VersionOne 9thState of Agile Survey
- 31. S O LV E D E P E N D E N C I E S E A R L Y , I N T E G R A T E O F T E N A PROJECT GETS DELAYED ONE DAY AT A TIME
- 32. DONâT ACCEPT EXCUSES A PROJECTGETS DELAYED ONE DAY AT A TIME
- 33. HOW TO APPLY #NOESTIMATES source:Keoni Cabral, some rights reserved
- 34. M A KE A L L W O R K V I S I B L E APPLY #NOESTIMATES source: Rich Savage, some rights reserved
- 35.
- 36. S T OP E V E R Y T H I N G T H A T I S N O T D E L I V E R I N G R E A L V A L U E MAKE ALL WORK VISIBLE
- 38. P R OJ E C T S H A V E H U G E O V E R H E A D W H E N T H E Y A R E L O N G - T E R M MAKE ALL WORK VISIBLE by Joseph Bylund, some rights reserved
- 39. DONâT START TOO MANYTHINGS IN PARALLEL MAKE ALL WORK VISIBLE
- 42. VISUALISE AND IDENTIFY THE QUEUESTHAT YOU HAVE APPLY #NOESTIMATES
- 43. START WITH THE TEAMS VISUALISEAND IDENTIFY THE QUEUES
- 44. AFTER THE TEAMSFIND ALL SUBMARINES AND ELIMINATE THEM VISUALISE AND IDENTIFY THE QUEUES
- 45.
- 46. GATHER THE DATA OFYOUR TEAMS PAST VELOCITY APPLY #NOESTIMATES
- 47. ONLY FOR COMPARABLE PERIODS INTIME GATHER TEAMS PAST VELOCITY
- 48. DONâT COUNT TASKS, BUGSAND OTHER GATHER TEAMS PAST VELOCITY
- 49. C R EA T E Y O U R F I R S T B U R N - U P APPLY #NOESTIMATES
- 50. H O WT O C R E A T E Y O U R F I R S T B U R N - U P 1. sum up all the Scope that you know of 2. donât break down future work (4- x months) 3. if you have a fixed end date add an âoptimumâ line 4. fill in the changed scope and finished scope every week or sprint 5. start managing the scope
- 57. S O ME C O M P A R I S O N APPLY #NOESTIMATES
- 58. Source: Vasco Duarte#NoEstimates presentation
- 59. #NoEstimates RegularEstimates âThe chart isa snapshot of one team of 20+ teams over a 2 year period.â â Cory Foy
- 60. NOW LET METELL YOU A SECRET
- 61. THE SECRET BEHIND #NOESTIMATES âąEvery team has their average story size âą Product Owners can learn how to create chunks of 1-3 days of work âą Teams can produce finished increments every sprint âą Youâll have the most accurate forecast ever FOR FREE
- 62.
- 63.
- 64. Disclaimer... This is onlyone project! Find 21 more at: http://bit.ly/NoEstimatesProjectsDB
- 65. After just 3sprints # of Stories predictive powerStory Points predictive power The true output: 349,5 SPs completed The predicted output: 418 SPs completed +20% The true output: 228 Stories The predicted output: 220 Stories -4%!
- 66. After just 5sprints # of Stories predictive powerStory Points predictive power The true output: 349,5 SPs completed The predicted output: 396 SPs completed +13% The true output: 228 Stories The predicted output: 220 Stories -4%!
- 67. S O ME S I M P L E M A T H APPLY #NOESTIMATES source: Dylan Ng, some rights reserved
- 68. S A MP L E C A L C U L A T E D C O S T O F D O I N G E S T I M A T E S F O R A O N E Y E A R P R O J E C T 5 Minute / Story Discussion x # Stories x # Number Team Members 5 x 5 x 8 = 200 Minutes x 2 weekâs sprints = 53/2 = ~25 sprints 25 x 200 = 5000 Minutes = 83 hours = ~3,5 days
- 69. STOP ESTIMATING NOWAND YOUâLL GAIN HALF A SPRINT EVERY YEAR
- 70. W R AP I T U P APPLY #NOESTIMATES source: Jim Bauer, some rights reserved
- 71. S C RU M A N D A L S O # N O E S T I M A T E S C A N N O T W O R K W I T H O U T X P VARIABILITY, COMPLEXITY, ACCIDENTAL COMPLICATION ARE NATURAL ENEMIES OF ESTIMATES CREATE TRANSPARENCY TACKLE YOUR CODE QUALITY AND FIX YOUR REQUIREMENTS FUNNEL
- 72.
- 73.
- 74.
- 75. THANK YOU! â SV E N S C H N E E , @ M R S N O W 7 6 , S V E N . S C H N E E @ O I K O S O F Y . C O M
Editor's Notes
- #60Â Here is a chart that Cory Foy posted on twitter just a few weeks ago.