Your SlideShare is downloading. ×
0
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Team Estimation Game
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Team Estimation Game

1,272

Published on

These slides are part of a presentation given at Silicon Valley code Camp 2009.

These slides are part of a presentation given at Silicon Valley code Camp 2009.

Published in: Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,272
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
15
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Team Estimation Game Workshop Silicon Valley Code Camp – October 2009 Estimating User Stories Without Numbers (Well, almost.)
  • 2. What is Complexity? Which item is more complex?
    • A 50-piece jigsaw puzzle
      • A 1000-piece jigsaw puzzle
  • 3. What is Complexity? Which task is more complex?
      • I want to arrange a trip to Disneyland.
      • 4. I want to arrange a trip to the Moon.
  • 5. What is Complexity? Which User Story is more complex?
      • As a user I want the system to remember my login information, so that I can log in faster.
      • 6. As a user I want the system to learn my preferences, so that I can work faster.
  • 7. What is Complexity? Working definition: The more complex thing is the thing with more interconnected parts (or steps). Something to remember: It is possible to estimate the relative complexity of User Stories without knowing how long they will take to implement.
  • 8. Estimation Problems
    • Excessive detail
    • 9. Estimation turns into design
    • 10. Attempting to achieve precision
    • 11. Reluctance to commit
    Estimates are really just best guesses based on current information. You'll have more information later.
  • 12. Estimation Without Numbers
    • Estimates are based on relative story complexity.
    • 13. Relative estimates are easier than absolute estimates.
  • 14. Game Play 1) Place Story Cards in pile on table. 2) First player places top card on playing surface. 3) Next player places top card on playing surface relative to first card. 4) Next player can either: Play top card from pile, or Move a card on the playing surface, or Pass 5) Repeat Step 4 until a) no more cards remain in pile, and b) no player wishes to move a card
  • 15. The Project Develop Website TeamEstimationGame .com User Story format: As a <type of user> I want <capability> , so that <business value> . Types of Users: 1) Customer 2) Developer
  • 16. The Project Estimate how long it takes to eat various kinds of fruit.
  • 17. Game Play “ Let the games begin.”
  • 18. Quantifying Complexity (This is the “almost” part) Saying how much more simple or complex than other Stories a particular Story is.
  • 19. Game Play 6) Place an estimate at the top of each column. 7) Change estimates until all team members agree.
  • 20. Questions ?

×