2. Agile - Iteration
it·er·a·tion
itəˈrāSHən
noun
the repetition of a process or utterance.
repetition of a mathematical or computational procedure
applied to the result of a previous application, typically as a
means of obtaining successively closer approximations to
the solution of a problem.
a new version of a piece of computer hardware or software.
plural noun: iterations
Charter : Confidential 2
4. Agile - Iteration
Stakeholder changes
Short Iteration = Less time for stakeholder to think of a change
The problems with longer time frames
• Teams learn to hide progress from the stakeholder until the end so they
can’t think of changes
• The “big review meeting” at the end to determine if the software satisfies the
contract
• The inevitable variances;
• software wasn’t built to spec
• software is exactly what was requested but doesn’t met a need
Charter : Confidential 4
5. Agile - Iteration
Faster time to workflow metrics
• How fast is the team finishing work?
• Does the team have the right skill balance?
• Identify systemic issues (e.g. firewall requests)
With metrics we can…
• predict when a work item will finish
• build a project/product road map
• create a baseline to improve on
Charter : Confidential 5
6. Agile - Iteration
Faster ROI reduces overall cost
• System development requires up front costs (hardware, people, etc)
• ROI begins when customers start using the system
• Fast time to market with smaller increments reduces accumulation of
unrealized value
• Finance sometimes calls this “opportunity cost”
Charter : Confidential 6
Valueunreleased
Time
Project Value Accumulation
Valueunreleased
Time
Short vs. Long Release Time
Release all features at project end Feature A Feature B Feature C
7. Agile - Iteration
• Checklist mentality
• Early understanding of
iteration status
• Certain amount of
gamification
• Physical interaction with
Kanban board, proven
increase in engagement
Charter : Confidential 7
Sense of accomplishment, closure