Iteration Types

Posted by Amr Elssamadisy on Jul 31, 2007

Sections

Process & Practices,

Architecture & Design

Topics

Scrum ,

Agile Techniques ,

Scaling Agile ,

Agile in the Enterprise ,

Methodologies ,

Programming ,

Agile ,

Criticism

What is an iteration in the Agile world? How is it different than previous ways the software community has performed iterations? Are there different types of iterations, and does it matter? The ScrumDevelopment list has been recently discussing type A, B, and C sprints (sprint = iteration in Scrum terminology) as defined by Jeff Sutherland and the ideas are relevant the the wider Agile community.

A majority of the Agile community would probably agree with the following definition of an iteration:

An Iteration is a constant time-box where the development team builds a part of the system completely as defined by the Done State. This allows the team to learn by taking a concept from requirements to as-close-as-possible to deployment and gives true visibility into project progress.

Furthermore, iterations run consecutively, the end of one iteration is immediately followed by the beginning of the next. This definition of iteration is different from earlier (pre-Agile) definitions mainly because of the Done State - pre-Agile iterations would build different parts of a function over multiple time-boxes without reaching completion.

So, from that basic understanding, here are three types of iterations as defined by Jeff Sutherland in Future of Scrum: Parallel Pipelining of Sprints in Complex Projects. This is their representation graphically:

The main difference is their overlapping. Type A has a 'breather' between iterations/sprints to give the team a chance to agree on the previous done-ness of one sprint/iteration while giving a time window for the requirements to be communicated and agreed upon for the next sprint.

Type B resembles the definition of iteration above. There is a little overlap of the work for sprints as the product owner/customer prepares requirements for the upcoming sprint/iteration to be finalized in the kickoff meeting for the next sprint/iteration.

Type C is used in program management to run multiple related product scrums concurrently. It seems to show the overlap in an organization that uses Scrum of Scrums. If this seems confusing or unclear, you are not alone; Serge Beaumont attempted to clarify the differences after Jeff Sutherland visited his organization.

So how is this important to the Scrum community and the larger Agile community? Some, like Ken Schwaber, believe this takes our focus away from really important issues:

I've been following the threads about type N, A, B, C and advanced Scrum. Although these may represent the engineering, personnel, and product management practices that an organization adopts as a result of Scrum's inspect and adapt, they aren't Scrum. I think we are mistaking the consequences of Scrum with Scrum itself. What may be most destructive about these supposed extensions is that they will divert people from the real work of Scrum ...

Others might feel that reflection and understanding of one of the cornerstone practices of Agile development is important. What do you think?

1. Back to top

   Concurrently or consecutively?

   by Yagiz Erkan

   Furthermore, iterations run concurrently, the end of one iteration is immediately followed by the beginning of the next.

   
   
   I think this should read consecutively rather than concurrently!
   
   - Yagiz -
   blog.decaresystems.ie

   Reply

2. Back to top

   Re: Concurrently or consecutively?

   by Sadek Drobi

   Furthermore, iterations run concurrently, the end of one iteration is immediately followed by the beginning of the next.

   
   
   I think this should read consecutively rather than concurrently!
   
   - Yagiz -
   blog.decaresystems.ie

   
   I agree, it scared me the word concurrently!
   I guess that it is not a good idea to try to illustrate sprints of Scrum-Of-Scrums. Scrum-Of-Scrums is a way of communication, and in my opinion it doesnt have its identifiable sprints. Trying to illustrate them something will result in a graphic that blurs the vision of what really goes on.
   
   Sadek Drobi

   Reply

3. Back to top

   Re: Concurrently or consecutively?

   by Amr Elssamadisy

   Good catch - corrected! Thanks - Amr

   Reply

4. Back to top

   true visibility?

   by Remember Objective

   On the one hand it is very difficult to evaluate the impact of any technique. On the other it seems inevitable that learning a technique means you end up forgetting the main objectives.
   
   The purpose of iteration is feedback. I didn't see that word once in the article. I didn't see the word "test".
   
   The purpose of feedback is "contact with problem", which is tactile-kinesthetic sense, not visual.
   
   The risk with these organized methodologies is that, even under the guise of "agility" (which means what now?), you end up with the illusion of progress. Illusion certainly depends on the visual modality.
   
   Agility to me means "hackability"--the ability to quickly setup feedback loops.

   Reply

5. Back to top

   Tried this overlapping thing once...

   by Miro Walker

   ...didn't really work.
   
   The problem for us came when we overlapped iterations it meant that we had already started the next iteration before we finished the last, so if some of the requirements in the first iteration weren't "done" at the end, they couldn't be rolled into the next, because that one had already started. They would (in theory) be pushed into iteration x+2, but in reality, that meant that we ended up losing the objective we were aiming for: working code.

   Reply