Iteration 2: Avoiding Risk

I l @ ve RuBoard

With a successful first iteration, you can get some work done. But take it easy ”you still have a new customer and perhaps a team that is not used to working together or with XP. Do easy stories in this iteration to get another success under your belt. Learn how the team works together and how well they estimate and improve their estimates each day. Give extra time to writing acceptance tests. Focus on getting started on the graphic design stories and some straightforward functional stories. Let the customer pick a fun functional story. Stay away from risk in this iteration ”working with a new team is risky enough.

The following stories implement sitemap.xml, your Web site. It may not be what your client had in mind for a release, but in theory it is complete and functional. In iteration 1 you set up the server, so now you are at a place four weeks into the project that waterfall Web projects won't reach for two to three more months. In waterfall projects the customer gets nothing until he gets everything. As an illustration, here are some obligatory stories from a typical second iteration:

The first few iterations are about finding project "risks"; deal with risks early or you may fall though the ice too far from shore.


  • Design candidates

  • Create sitemap.xml and run site structure script

  • Content catalog of what is available for the project

  • Content collection ”"Who We Are"

  • Content collection ”"What We Do"

I l @ ve RuBoard

Extreme Programming for Web Projects
Extreme Programming for Web Projects
ISBN: 0201794276
EAN: 2147483647
Year: 2003
Pages: 95

Similar book on Amazon © 2008-2017.
If you may any questions please contact us: