 Iteration
After a suitable project has been chosen, participants play XP's Planning Game to produce an
iteration plan. This involves formulating the team's velocity, identifying tasks to complete for
each story, estimating tasks, negotiating task scope, signing up for tasks and creating the iteration
poster. During the iteration, programmers, customers and coaches will all have a chance to work together.
Here is what each party will do:
Programmers will
-
discuss/agree on a simple design
-
pair program
-
do test-driven development
-
mercilessly refactor
-
continuously integrate
-
practice collective code ownership
-
help customers automate customer tests
Customers will
-
answer questions from programmers and work with them to automate customer tests
-
certify that tasks from iteration poster are complete
Coaches will
-
help programmers and customers
-
facilitate design discussions and stand-up meetings
At the end of the iteration, the group will conduct a short iteration retrospective to discover what
"Worked Well" or "Needed Improvement" during the iteration. The activity concludes with a debrief, which is
a chance for the whole team to reflect on what surprised, delighted, confused or annoyed them, explore what
it was like to implement XP and discern how XP's values were or were not present during the iteration.
Flavor: 6-hour
340 to 360 minutes
This version, which is recommended for teams who have never completed a technical XP iteration, gives participants ample
time to do planning, coding and debriefing.
ID: 13A |
Flavor: 5-hour
260 to 300 minutes
This version, which is recommended for those who have already taken the 6-hour version, gives participants sufficient time
to do planning, coding and debriefing.
ID: 13B |
Flavor: 4-hour
220 to 240 minutes
This version, which is recommended for those who have already taken the 5-hour version, gives participants just enough time
to do planning, coding and debriefing.
ID: 13C |
|
|
 
|
Catalogs