Kane Mar

Update: Ed Gibbs writes (here) about some of the challenges that he’s facing within his organization. Interesting stuff.

I like two week iterations. The short timeframe ensures quick feedback, and makes the team more responsive to the Product Owners needs. But two week iterations can be very uncomfortable for teams that are familiar with delivery cycles that span months. One of the very first issues that is raised is that the team does not have sufficient time to be “done”.

Typically what this means is that the software will be code complete at the end of an iteration, but will not have been fully tested. It usually gets delivered late and hence there is insufficient time for full and rigorous testing. After the third of forth sprint it’s common for a team to ask me if we can change to three (or four) week iterations to “allow more time for testing.“
Read the rest of this entry »