This thread discusses the Content article: An Agile Approach To Managing Distributed Development

Several people pointed out that the original visual in this article made the process look very waterfall-ish. This is a fair criticism, and the visual has been updated.

The intent of the original visual was to point out that there is some analysis activity on stories we suspect we'll get to in the subsequent iteration if for no other reason than to make more informed decisions, particularly for estimating.  We also see QA activity lagging, again usually an iteration.  I didn't mean to suggest that analysis and QA happen in exclusivity and as separate workstreams to development, or suggest that these workstreams preclude involvement of the business or an analyst or QA during a development iteration, or suggest that the requirements can't change in-flight during development.  However, it seems the visual strongly suggested these things.  That was unintended.

I do appreciate everybody's comments and feedback. The visual has been updated.