Agile effort estimation


Published on

Agile effort estimation presentation done at the Israeli "R&D management forum"

Published in: Technology
1 Comment
  • hi there, there is a mobile application for effort estimation and basic time planing, have alook at
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Agile effort estimation

  1. 2. Effort estimation in agile projects Elad Sofer - Agile coach & Scrum master. Infrastructure scrum master – Nokia Siemens networks blog - LinkedIn -
  2. 3. How to estimate this task ?
  3. 4. What makes estimation agile ? <ul><li>Effort estimation Is not considered as a phase in the project </li></ul><ul><li>Changes are expected, embrace change. </li></ul><ul><li>Estimations are easily correctable. </li></ul><ul><li>Estimate by feature not by activity </li></ul><ul><li>Estimate by a multi-disciplinary team. </li></ul><ul><li>And… </li></ul>
  4. 5. “ It’s better to be roughly right than precisely wrong.” [John Maynard Keynes [
  5. 6. Persistence of time
  6. 7. How long will it take to… <ul><li>Read the bible </li></ul><ul><li>Drive to Paris ? </li></ul><ul><li>Solve a math equation ? </li></ul><ul><li>Add support for LDAP ? </li></ul>
  7. 8. 34.4
  8. 9. Estimate tasks in relative size <ul><li>We are not good in measuring absolute values. </li></ul><ul><li>We are good in comparing things. </li></ul><ul><li>We have the basic math skills (or a calculator). </li></ul><ul><li>High accuracy has a high toll. </li></ul><ul><li>Estimates become commitments </li></ul><ul><li>Time is not persistent. </li></ul>
  9. 10. Story points <ul><li>Name is derived from user stories. </li></ul><ul><li>They reflect the “bigness” of a user story. </li></ul><ul><ul><li>How hard it is ? </li></ul></ul><ul><ul><li>How risky it is ? </li></ul></ul><ul><ul><li>How much of it there is ? </li></ul></ul><ul><li>Relative values matters. </li></ul><ul><li>Unitless. </li></ul><ul><li>Point values “include uncertainty”. </li></ul><ul><li>Easy and quick </li></ul><ul><ul><li>A little effort helps a lot </li></ul></ul><ul><ul><li>A lot of effort helps a little more </li></ul></ul>
  10. 11. Estimation techniques <ul><li>Expert opinion </li></ul><ul><li>Analogy </li></ul><ul><li>Educated guess </li></ul><ul><li>Disaggregating </li></ul><ul><li>Planning poker </li></ul>
  11. 12. Planning poker <ul><li>Each person gets a deck of cards. </li></ul><ul><li>The item to be estimated is read to all. </li></ul><ul><li>Attendants ask clarifications for the item. </li></ul><ul><li>Each person selects a card and puts it on the table facing down. </li></ul><ul><li>When everyone is done, cards are exposed. </li></ul><ul><li>If the estimations do not match a short discussion is done. -> Goto 4. </li></ul><ul><li>Handle next item. </li></ul>
  12. 13. Why planning poker works ? <ul><li>Those who do the work estimate it. </li></ul><ul><li>Emphasizes relative estimation </li></ul><ul><li>Estimates are within one order of magnitude. </li></ul><ul><li>Reduces anchoring - Everyone's opinion is heard. </li></ul>
  13. 14. Specification length <ul><li>One page spec </li></ul><ul><li>Group A </li></ul><ul><li>7 Pages spec </li></ul><ul><li>Group B </li></ul>173 hours 117 hours
  14. 15. Irrelevant information <ul><li>Group A </li></ul><ul><li>added irrelevant details: </li></ul><ul><ul><li>End user desktop apps </li></ul></ul><ul><ul><li>Usernames & passwords </li></ul></ul><ul><ul><li>Etc. </li></ul></ul><ul><li>Group B </li></ul>39 hours 20 hours
  15. 16. Extra requirements <ul><li>Requirements 1-4 </li></ul><ul><li>Group A </li></ul><ul><li>Requirements 1-5 </li></ul><ul><li>Group B </li></ul>4 hours 4 hours <ul><li>Requirements 1-5 but told to estimate 1-4 only </li></ul><ul><li>Group C </li></ul>8 hours
  16. 17. Given anchor <ul><li>Group A </li></ul><ul><li>Customer thinks 500 </li></ul><ul><ul><li>customer has no technical knowledge </li></ul></ul><ul><ul><li>Don’t let the customer influence you </li></ul></ul><ul><li>Group B </li></ul>555 hours 456 hours <ul><li>Same as B customer thinks 50 </li></ul><ul><li>Group C </li></ul>99 hours
  17. 18. Why planning poker works ? <ul><li>Those who do the work estimate it. </li></ul><ul><li>Emphasizes relative estimation </li></ul><ul><li>Estimates are within one order of magnitude. </li></ul><ul><li>Reduces anchoring - Everyone's opinion is heard. </li></ul><ul><li>Modeled for open discussion – forces thinking. </li></ul><ul><li>It’s quick & fun ! </li></ul>
  18. 19. How to calculate time ? S V T
  19. 20. Velocity <ul><li>How many points can the team complete in one iteration. </li></ul><ul><li>Easy to measure. </li></ul><ul><li>Fixes estimation errors. </li></ul><ul><li>Easily reflects the project status. </li></ul><ul><li>Primary parameter in planning. </li></ul>
  20. 21. Burn down charts <ul><li>Increase visibility </li></ul><ul><li>Easy to understand. </li></ul><ul><li>Updated automatically & immediately. </li></ul><ul><li>Usually used on release & sprint level. </li></ul>
  21. 22. So what will it be ? vs + +
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.