Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Scrum + Kanban = Scrumban

DZone 's Guide to

Scrum + Kanban = Scrumban

Scrumban is a hybrid of scrum and kanban process, taking the best of both agile worlds.

· Agile Zone ·
Free Resource

While much is written about the 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 = Scrum + Kanban

Let’s see main the characteristics of both methodologies:

Scrum

  1. Cross-functional, self organized teams
  2. Time boxed approach where iterative development leads to potentially shippable code
  3. Inspect and adapt approach
  4. A prioritized list of features to be worked upon in a given sprint

Kanban

  1. Visualize workflow
  2. Use named column to indicate current state of item in workflow
  3. 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 desks
  • Projects with frequent and unexpected user stories

Here is a typical workflow or Kanban board for maintenance project:

Image title

Why scrumban is suitable for a 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 us more realistic information (i.e. a time a ticket takes to complete) measured from when it is first began
  • You can still use sprint retrospectives to identify what was done right and what can be improved
Topics:
scrumban ,agile ,scrum ,kanban

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}