Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Comparison of different Agile Iterative process approaches

1,794 views

Published on

Interested in the difference between Iterative/Mini-waterfall/Scrum/Kanban/ScrumBan modes of delivery? Maybe this schematic comparison can help

Published in: Business

Comparison of different Agile Iterative process approaches

  1. 1. Iterative Approach Mini-Waterfalls Working Tested• Within each Iteration – Still looks like Software Increment a mini-waterfall (with uneven work load, feedback towards end of cycle, etc. )• Improves Feedback• Painful to execute by teams – that ST Cycle Design strive for longer and longer iterations SST Fixing• Ineffective Coding• Reasonable stepping stone sometimes
  2. 2. Scrum Sprints Working Tested• Real Even flow within each iteration Software Increment• Even earlier feedback• Better chance for having Working Tested Software each Sprint• More sustainable since even flow across people• Requires very small stories – Investment in Planning• Very hard to really achieve
  3. 3. Real Flow - Kanban Working Tested• Real Even Flow w/o timeboxes Software Increment• Iterate just at the level of the work items• Even more sustainable – Less stress/idle cycles.• Small stories preferred but can live better with exceptions• Lack of timebox has pros and cons, depending on the context.
  4. 4. Real Flow - ScrumBan Working Tested• Real Even Flow. Iterations just Software review/delivery checkpoints that do Increment energize the people without over- stressing them• Even more sustainable – Less stress/idle cycles.• Small stories preferred but can live better with exceptions• More pragmatic• Preferred choice of many organizations today – Evolution of Scrum using Kanban

×