Iteration Burn Down | Glossary

Definition

The ‘Iteration Burndown’ displays the remaining work and the amount completed within the iteration. It is to be proactively anticipated whether the committed work will be able to get delivered by the iteration end date. It’s also useful during iteration retrospective meetings to help identify events during the iteration, or planning.

The features comprised include:

  • Blue bars for remaining task hours
  • Green bars for completed story points
  • Ideal burndown rate is a black line, based on task estimate
  • Hover over the bars/line to see detailed figures on current/past progress.

Further Reading

  • “Agile & Iterative Development : A Manager’s Guide 1st Edition” (book), by  Craig Larman.

 

Iterative Development | Glossary

Definition

Iterative Development is a method that breaks down the large workload of a Software Development process into smaller chunks, and in cycles. The featured code is designed, developed and tested in continuous repeated cycles. Features are added/subtracted after each iteration so as to develop the software in its best possible condition to be deployed.

Iterative development is a key practice in Agile Development Methodology. It is a contrast with the traditional Waterfall Method, in which Development Cycle is ‘Gated’. The purpose of working in iterations is to allow more flexibility and change.  Every cycle brings more possibilities of improving the functionality of the product and towards finally building a great end product.

Further Reading

  •  “Agile and Iterative Development Complete Self-Assessment Guide” (book), by Gerardus Blokdyk .