The document discusses using a card game workshop to estimate the relative complexity of user stories without assigning specific time estimates. Players arrange story cards from least to most complex based on the interconnectedness of their parts. Estimates are then placed at the top of each column and adjusted until the team reaches consensus. The game aims to address common problems with estimation like excessive detail, reluctance to commit, and imprecision by focusing on complexity rather than time.
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.
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