Team Estimation Game Workshop Silicon Valley Code Camp – October 2009 Estimating User Stories Without Numbers (Well, almost.)
What is Complexity? Which item is more complex? <ul><li>A 50-piece jigsaw puzzle </li></ul><ul><ul><li>A 1000-piece jigsaw puzzle </li></ul></ul>
What is Complexity? Which task is more complex? <ul><ul><li>I want to arrange a trip to Disneyland.
I want to arrange a trip to the Moon. </li></ul></ul>
What is Complexity? Which User Story is more complex? <ul><ul><li>As a user I want the system to remember my login information, so that I can log in faster.
As a user I want the system to learn my preferences, so that I can work faster. </li></ul></ul>
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.
Reluctance to commit </li></ul>Estimates are really just best guesses based on current information. You'll have more information later.
Estimation Without Numbers <ul><li>Estimates are based on relative story complexity.
Relative estimates are easier than absolute estimates. </li></ul>
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
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
The Project Estimate how long it takes to eat various kinds of fruit.