Why scrum is so popular because it is a framework. A framework in turn is an abstraction or structure which helps in building something more meaningful and that can expand.
While much is written about advantages of scrum over traditional approaches like waterfall, in a single line it makes things easier for all the stake holders of project.
Kanban on the other hand is a lean manufacturing process. It is used for logistic control system.
Kanban is a Japanese term which means “Visual board” or “Card you can see”.
Scrumban is a hybrid of scrum and kanban process.
Scrumban = Srucm + Kanban
Let’s see main characteristics of both methodologies
Scrum:
- Cross-functional, self organized teams.
- Time boxed approach where iterative development leads to potentially shippable code.
- Inspect and adapt approach
- A prioritized list of features to be worked upon in a given sprint
Kanban:
- Visualize workflow
- Use named column to indicate current state of item in workflow
- Limit work in process: By assigning explicit limit on items in work it helps a lot for situations where there is a constant need for re- reprioritization of items and task switching.
Scrumban can be used :
- For maintenance of different applications
- For event-driven work like IT support – help-desk
- Projects with frequent and unexpected user stories.
Here is a typical workflow or Kanban board for maintenance project
Why scrumban suits for maintenance project:
- High priority / show stopper items can popup any time
- Need to work on items as and when they appear. No prioritized and committed PBIs
- Still go in a time boxed approach using scrum with having limit on WIP
- Can easily visualize work items
- Instead of velocity, a kanban metric cycle time is used which gives is more realistic information i.e. a time a ticket takes to complete; measured from when it is first began.
- You can still use sprint retrospective , to identify what was done right and what can be improved
TechnoTravey 