I was talking with a friend over the weekend about the collapsing the gantt chart graphic (see post below). Unfortunately, I realized that this graphic can give the impression that I'm recommending mini-waterfalls within each iteration. Although many teams new to agile start out in mini-waterfalls, this approach should not be the end goal. The ultimate goal is to have a dedicated team of people who can work in a cross-functional, role-sharing manner in order to meet the commitment for the sprint. This means that the BA may write tests, the DBA might code, the programmer might help write tech doc, and so forth, while many of the tasks are happening in parallel (or in some cases, test first). Quite different from a 'mini-waterfall.' I will revisit this graphic and include an update in a later post.