Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Statistical Forecasting: Estimation made easy (...

Statistical Forecasting: Estimation made easy (ABE)

Instead of relying on vulnerable human memory we use the actual historical data and run statistical simulations to produce a forecast. Not only is the outcome significantly better than what expert guess provides but also it requires less work from development teams.

Avatar for Tomek Rusiłko

Tomek Rusiłko

October 11, 2016
Tweet

More Decks by Tomek Rusiłko

Other Decks in Technology

Transcript

  1. IF A PROJECT HAS NO RISKS, DON'T DO IT. Tom

    DeMarco & Timothy Lister DON’T DO IT T. DEMARCO, T. LISTER: WALTZING WITH BEARS
  2. ACCURACY IN ESTIMATING DID NOT IMPROVE AS INFORMATION ACCUMULATED, WHILE

    CONFIDENCE INCREASED CONSISTENTLY. Claire Tsai, Joshua Klayman, Reid Hastie ACCURACY OF ESTIMATION SOURCE: TSAI, KLAYMAN, HASTIE: EFFECTS OF AMOUNT OF INFORMATION ON JUDGMENT ACCURACY AND CONFIDENCE
  3. SCIENTISTS AND WRITERS ARE NOTORIOUSLY PRONE TO UNDERESTIMATE THE TIME

    REQUIRED TO COMPLETE A PROJECT, EVEN WHEN THEY HAVE CONSIDERABLE EXPERIENCE OF PAST FAILURES TO LIVE UP TO PLANNED SCHEDULES. A SIMILAR BIAS HAS BEEN DOCUMENTED IN ENGINEERS' ESTIMATES. Daniel Kahneman, Amos Tversky ESTIMATION BIAS
  4. COUNTING THE NUMBER OF STORIES METRIC DOESN'T TAKE THE SIZE

    INTO ACCOUNT. IT TURNS OUT IT DOESN'T MATTER. THE SIZE OF STORIES IS GELLED TO A VERY COMMON SIZE. WE COULD USE THROUGHPUT VERY SUCCESSFULLY WITH THE RESEARCH. Larry Maccherone THROUGHPUT VS STORY POINTS
  5. JAREK’S TASK HISTORY story start date end date #1 2016

    / 02 / 29 2016 / 03 / 02 #2 2016 / 02 / 29 2016 / 03 / 03 #3 2016 / 02 / 29 2016 / 03 / 01 2016 / 03 / 03 2016 / 03 / 03 2016 / 03 / 04 2016 / 03 / 04 2016 / 03 / 05 2016 / 03 / 05 2016 / 03 / 06 2016 / 03 / 06 2016 / 03 / 07 2016 / 03 / 07 #10 2016 / 03 / 08 2016 / 03 / 08
  6. Mon Tue Wed Thur Fri Week 1 Week 2 Week

    3 Week 4 JAREK’S TASK HISTORY
  7. Mon Tue Wed Thur Fri 1 1 2 1 1

    1 2 1 3 2 LEAD TIME
  8. 1 1 2 2 3 2 LEAD TIME DISTRIBUTION Lead

    Time Count 1 Day 6 60% 2 Days 3 30% 3 Days 1 10% Total 10 1 1 1 1
  9. LEAD TIME DISTRIBUTION 2 Days 3 Days 1 Day 1

    1 2 2 1 1 2 2 3 1 16 Total Lead Time Days
  10. LEAD TIME DISTRIBUTION FOR 10 TASKS IN THE BACKLOG 2

    Days 3 Days 1 Day 1 1 2 2 1 1 2 2 3 1 16 Total Lead Time Days
  11. LEAD TIME DISTRIBUTION FOR 10 TASKS IN THE BACKLOG 2

    Days 3 Days 1 Day 1 1 2 2 1 1 2 2 3 1 16 Total Lead Time Days
  12. Mon Tue Wed Thur Fri Week 1 Week 2 Week

    3 Week 4 JAREK’S TASK HISTORY
  13. Mon Tue Wed Thur Fri Week 1 Week 2 Week

    3 Week 4 JAREK’S TASK HISTORY
  14. Mon Tue Wed Thur Fri Week 1 Week 2 Week

    3 Week 4 JAREK’S TASK HISTORY
  15. Mon Tue Wed Thur Fri Week 1 Week 2 Week

    3 Week 4 JAREK’S TASK HISTORY
  16. Mon Tue Wed Thur Fri Week 1 Week 2 Week

    3 Week 4 JAREK’S TASK HISTORY 0 0 0 0 0 2 0 1 1 1 1 1 1 1 1 1 1 1 1 1
  17. WORK IN PROGRESS 1 Task 0 Tasks 2 Tasks SIMULATE

    THE NUMBER OF TASKS JAREK WORKS ON IN A DAY
  18. 1 Task 0 Tasks 2 Tasks WORK IN PROGRESS SIMULATE

    THE NUMBER OF TASKS JAREK WORKS ON IN A DAY 1 0 0 DAY 1: DAY 2: DAY 3: …
  19. 1 Task 0 Tasks 2 Tasks WORK IN PROGRESS SIMULATE

    THE NUMBER OF TASKS JAREK WORKS ON IN A DAY 1 0 0 DAY 1: DAY 2: DAY 3: …
  20. WORK IN PROGRESS Each square represents a work day 1

    1 Lead Time Days 1 Work Days Days
  21. WORK IN PROGRESS Each square represents a work day 1

    0 1 Lead Time Days 2 Work Days Days
  22. WORK IN PROGRESS Each square represents a work day 1

    0 0 1 Lead Time Days 3 Work Days Days
  23. WORK IN PROGRESS Each square represents a work day 1

    0 0 3 Lead Time Days 4 Work Days Days 2
  24. WORK IN PROGRESS Each square represents a work day 1

    2 1 0 1 1 0 1 0 1 1 1 1 2 0 1 2 0 16 Lead Time Days 18 Work Days Days
  25. 0 250 500 750 1000 Workdays 9 10 11 12

    13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
  26. 0 250 500 750 1000 Workdays 9 10 11 12

    13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 50%
  27. 0 250 500 750 1000 Workdays 9 10 11 12

    13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 50% 90%
  28. 90% CONFIDENCE LEVEL MEANS THAT OUR ESTIMATE IS CORRECT 9

    TIMES OUT OF 10. KINDA. Pawel Brodzinski 90% CONFIDENCE INTERVAL?
  29. ANY PROPOSED FORECASTING METHOD JUST HAS TO BE BETTER THAN

    WHAT YOU DO NOW, OR AT LEAST LESS EXPENSIVE WITH A SIMILAR RESULT. Troy Magennis BE BETTER
  30. SOURCES & RESOURCES ▸ Troy Magennis original work: http://www.lkce13.com/videos/magennis/ ▸

    http://focusedobjective.com/wp-content/uploads/2013/05/Modeling-and-Simulating-Software- Projects-Troy-Magennis.pdf ▸ http://blog.lunarlogic.io/2016/how-we-estimate-at-lunar-logic/ ▸ https://www.chicagobooth.edu/research/workshops/marketing/archive/workshoppapers/s06/tsai.pdf ▸ Planning Fallacy: https://books.google.pl/books?id=R- syxO7M67AC&pg=PA9&q=&redir_esc=y#v=onepage&q&f=false ▸ https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp/0374533555 ▸ Flow efficiency: https://hakanforss.wordpress.com/2014/06/17/flow-thinking-aceconf/ ▸ http://zsoltfabok.com/blog/2013/12/flow-efficiency/ ▸ https://www.infoq.com/presentations/agile-quantify ▸ http://brodzinski.com/2015/02/story-points-velocity-the-good-bits.html ▸ https://estimation.lunarlogic.io/ ▸ https://www.agilealliance.org/estimation-and-forecasting/ ▸ Projectr: http://getprojectr.com/