Iteration Planning Instructions
- Report completion status of last iteration's cards.
- Completed means Done. Finished. Unit tested. Integrated. Acceptance tested. Reviewed.
- Ask questions to clarify the story
- Ask, “How would you know if this story were completed successfully?”
- Suggest ways to make the story cheaper
- Discuss the work that will need to be done to complete the story
- Completed means Done. Finished. Unit tested. Integrated. Acceptance tested. Reviewed.
- Discuss the work that will need to be done to verify the story is completed
- Revise story card if new information comes up (Add Information, Split/Defer, Spike)
- Estimate in points, not time
- Estimate relative to other tasks the team has done
- Pick the optimistic estimate
- Write the estimate on the card
- Repeat for each card.
- Select the cards for this iteration, budgeting for about as many points as got completed last iteration
- Remember, Completed means Done. Finished. Unit tested. Integrated. Acceptance tested. Reviewed.
- Group cards by priority, High, Medium, Low
- Sign up for High priority cards until they're gone
- Sign up for Medium priority cards until they're gone
- Sign up for Low priority cards as desired
- It's OK to leave (low priority) cards on the table
- Discourage individuals from signing up for too much (# points completed last time / # of team members)
Source: Kent Beck. 2005. Extreme Programming Explained, 2nd edition, 46-47. Pearson Education, Inc. (Variations by Kay Johansen.)