We Iterate...So We're Agile?
Working with iterations does not automatically make you an agile team. It doesn't even necessarily mean that you are using iterative development. Paradoxically, it is possible to be agile without use of iterations. This is true if your team is utilizing Kanban, for example.
Let’s get into details...
What is the iterative development?
"Iterative development acknowledges that we will probably get things wrong before we get them right and that we will do things poorly before we do them well." (Goldberg and Rubin 1995).
Iterative development can be compared with an idea that is transformed into a rough prototype of a product that evolves and becomes better over time. Most likely it will be quite a crude product as it may miss many features. The good news is that it will allow us to get fast feedback and decide if we want to move on or not.
Jeff Putton gives a brilliant example with a portrait of Mona Lisa that demonstrates iterative development approach:

I need to point out here that this example is exaggerated. What I mean is that you do not necessarily have to “iterate" the whole product at once. Iterative development simply supposes any change made not requiring obligatory global changes throughout a product.
What is the incremental development?
Incremental development implies adding a piece after
Please log in or sign up below to read the rest of the article.
|
"Too many pieces of music finish too long after the end." - Igor Stravinsky |




