ExtremeLegoWorkshopTrial

IMO some of this is due to the lack of previous exposure to XP, but this is useful as it shows how to adapt the workshop for this audience.

FeedBack? - Tracker Role The tracker needs a more definate role. Suggest explicitly encouraging a few key XP values such as refactoring, short iterations, etc.. Also ensuring an EngineeringTask? 'goal for the iteration' is defined by the team.

FeedBack? - Timing of the slideshow I also reworked the slides, but people still found the first iteration confusing. We may now consider de-emphasising XP at the start - simply stating the rules of the workshop. At the end, we may consider the list of "what worked, what didn't work" from each team and relating these back to the XP practices.

FeedBack? - OnsiteCustomer? It seems important to emphasize the on-site customer. I believe the team that most uses the on-site customer should see some benefit over the other teams. I'm thinking that at each baseline the team can ask the customer what he thinks (a kind of functional test), which would allow feedback either in the form of extra stories, or clarifications on existing stories. (opinions on this please?)

³host³³date³August 2, 2000³agent³Mozilla/4.5 en? (WinNT?; I)³ExtremeLegoWorkshopTrial