T3 conasia agile estimating

293 views

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
293
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

T3 conasia agile estimating

  1. 1. Better Plan your TYPO3 Projects with Agile EstimatingVioleng Mamvioleng@web-essentials.asia
  2. 2. Violeng Mam● BA in Computer Sciences● TYPO3 certified Integrator● Project Manager and Team leader Project Managers Team● Senior Manager at Web Essentials● 4 years experience working with international clients
  3. 3. Agenda Problems with Estimates Agile Estimating  Relative Estimates  Velocity  Our Experience with AE Summary
  4. 4. How many balls?
  5. 5. Estimate Vs Guess
  6. 6. Why Plan?● Keep due dates and budget● Manage resources● Build trust with clients● Reduce risks and last minute surprises● Create a basis for decision making→ Control the outcome/future of a project
  7. 7. Problems with Estimations● Its hard to know exactly how long a task will take● People are not very good at giving accurate estimates● Sometimes it takes longer than thought● Sometimes we find unexpected problems● People get sick, take holidays...● Planning by hour or day gives wrong incentive● Activities are interdependent
  8. 8. Activity: Country Sizes South-East AsiaSource: wolframalpha.com
  9. 9. Activity: Country Sizes CambodiaSource: wolframalpha.com
  10. 10. Activity: Country Sizes Cambodia LaosSource: wolframalpha.com
  11. 11. Activity: Country Sizes Cambodia Laos ThailandSource: wolframalpha.com
  12. 12. Activity: Country Sizes Cambodia Laos Thailand VietnamSource: wolframalpha.com
  13. 13. Activity: Country Sizes Cambodia Laos Thailand Vietnam MyanmarSource: wolframalpha.com
  14. 14. Activity: Country Sizes Cambodia: 181,035 km2 Laos: 236,800 km2 Thailand: 513,120 km2 Vietnam: 329,560 km2 Myanmar: 676,578 km2Source: wolframalpha.com
  15. 15. Activity: Country Sizes Cambodia: 181,035 km2 Laos: 236,800 km2 Thailand: 513,120 km2 Vietnam: 329,560 km2 Myanmar: 676,578 km2 Germany: 357,022 km2 Switzerland: 41,277 km2Source: wolframalpha.com
  16. 16. Activity: Country Sizes Cambodia: 1 country pt. Laos: ? Thailand: ? Vietnam: ? Myanmar: ?Source: wolframalpha.com
  17. 17. Activity: Country Sizes Cambodia: 1 country pt. Laos: 1 cpt. Thailand: 3 cpts. Vietnam: 2 cpts. Myanmar: 4 cpts. Germany: 2 cpts. Switzerland: ¼ cpts.Source: wolframalpha.com
  18. 18. Activity: Country SizesIt is easier to compare in country points than in actual sizes.→ Relative Estimations
  19. 19. Relative EstimationsIt does not matter what unit we use to measure the size:● Country Points● Ideal days● Bananas...It is important that the estimates are consistent:Same sizes get same number of points
  20. 20. Relative Estimations
  21. 21. Relative Estimations
  22. 22. Relative EstimationsBuilding estimates on facts:If an activity takes longer the chances are high that a similaractivity takes longer, too.→ Velocity will define the time needed
  23. 23. Velocity● Velocity is the number of country points or ideal days wecan do in a set time (e.g. a week)● Things like interruptions, meetings, infrastructure failures willlower our velocity● Velocity can tell us when we will be finished
  24. 24. Velocity
  25. 25. Example ProjectImage Contest● Users can upload images● Users can view uploaded images and rate● The Winners are displayed and notified
  26. 26. Example Project Picture Detail Concept, Generate (Lightbox) Data Model Extension & TCA Picture Gallery Load more when scrolling down Vote & Comment Functionality Highscore Send Email Image Functionality Upload
  27. 27. VelocitySimplified: All 9 tasks are the same sizeAssume: After 1 week, 3 tasks finished(simplified) Velocity = 3 tasks / 5 days = 0.6 tasks / day
  28. 28. VelocityWhen will we finish?● Remaining: 6 tasksSo we can complete (simplified):6 tasks / 0.6 tasks/day = 9 days**if we continue with the same velocity, but:Velocity will get more reliable if tracked over longer period
  29. 29. Example Project Picture Detail Techn. Concept, Generate (Lightbox) Data Model Extension & TCA Picture Gallery 1 ½ View 1 2 Load more when scrolling down Vote & Comment Functionality Highscore Send Email 1 Image 2 Upload 1 Functionality 2 2
  30. 30. VelocityTotal number of points: 12.5Assume:● 3.5 points finished● 3 days elapsed(simplified) Velocity = 3.5 points / 3 days = 1.2 points / day
  31. 31. VelocityWhen will we finish?● Remaining: 9 pointsSo we can complete (simplified):9 points / 1.2 points/day = 7.5 days → 8 daysProposition: It is better to track the points we cancomplete/week than the remaining days.
  32. 32. Increase accuracy● Involve the whole team in estimating● Use non-linear sequences for points such as e.g. Fibonacci: 0, (½), 1, 1,2, 3, 5, 8, 13, 21, …● Man-days instead of elapsed time for velocity calculation● Clearly define what means a task is complete● Verify velocity on a regular basis● Re-estimate stories if needed (but only if the relative size is wrong –absolute errors will be corrected by velocity)
  33. 33. Our Experience Planned and actual completion and scope 180 160 140 120 100 Total Planned Capacity Total Scope Points 80 Total Dev Complete 60 40 20 0 0 1 2 3 4 5 5 5 6 7 8 9 10 11 12 13 14 15 16 16 17 Iteration
  34. 34. How to decrease time to finish● Less interruptions and less multi-tasking (velocity +)● Give team members more time on project (man days +)● Add skilled developer to the team (velocity +, man days +)● Reduce scope of features or project (points -)
  35. 35. SummaryEstimating is a continuous process as we understand moreabout how we perform→ agile = flexible, well coordinated, quick to move
  36. 36. SummaryAgile Estimating will make your planning more accuratebecause: ● The whole team is involved ● Estimates of size and duration are separated ● Estimates and plans are based on facts ● Learning and adjusting is fostered→ Accurate estimates allow for better decision making
  37. 37. Further ReadingAgile Estimating and Planningby Mike Cohn
  38. 38. Q&A
  39. 39. Thank You!violeng@web-essentials.asia

×