Scribd
Upload
318 views1 page

Agile: Incremental vs Iterative Explained

Agile development is both incremental and iterative. It is incremental in that each iteration produces an increment of working functionality to release. It is iterative in that it allows for vague ideas to evolve into realizations through iterations, making course corrections along the way as understanding improves. Iterations allow decisions to be made later in the process, making changes easier and cheaper than if all decisions were made upfront.

Uploaded by

omar ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
318 views1 page

Agile: Incremental vs Iterative Explained

Agile development is both incremental and iterative. It is incremental in that each iteration produces an increment of working functionality to release. It is iterative in that it allows for vague ideas to evolve into realizations through iterations, making course corrections along the way as understanding improves. Iterations allow decisions to be made later in the process, making changes easier and cheaper than if all decisions were made upfront.

Uploaded by

omar ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Is Agile Incremental or Iterative ?

The product increment is the thing you produce at the Agile = incremental + iterative
end of an iteration, but there is more to it than that…

Jeff Patton used the infamous Mona Lisa


to illustrate the conce ptual difference :

Incrementing calls for a fully formed idea right from the start.
It’s not that different from waterfall then.

decisions are Karl Scotland introduced the conce pt of fidelity to capture


made early on w hat happens w hen work is done iteratively.
making things
hard to change Profile
High fidelity
solution
Iterating allows to move from vague idea to realisation, making
course correction as you go. Low fidelity Release 3

solution
Release 2

Changes are much Release 1

Easier & cheaper


Fidelity
!= quality

The Agile Broadcast, by David Michel This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

You might also like