Over a million developers have joined DZone.

Kanban or Scrum?

DZone's Guide to

Kanban or Scrum?

· ·
Free Resource

Can't decide which better fits your team? While Kanban is very light, basically focusing on visual workflow and WIP limits and leaving all the responsibilities to the team, Scrum has far more rules defining team, roles, work organizing and more. 

In addition to this, Scrum is better spread and more often applied. Of course, everything depends on the team and project it's working on. Actually, the best decision is to try both, identify certain Kanban and Scrum practices that work best for the team and then configure a custom Scrum-ban process which doesn’t burden your team with useless rules and increases the productivity of the team the most.

The easiest and fastest way to try both methods and then to create your own process is to use some Agile tool which supports Kanban, Scrum and custom processes. Eylean is a flexibly configurable virtual task board. You can start with a predefined task board configuration and improve it whenever you need. For example, you may start with a Scrum board, following all the Scrum rules, after some time decide which Scrum practices seem useless for your team, eliminate them and adopt such Kanban practices as extended Work In Progress section or WIP limits.

The picture below shows a sample Scrum-ban task board:

 Eylean_Kanban and Scrum board

 Separate columns that indicate different stages a task goes through until it’s done instead of a single Doing column. WIP limits set for each column in Work In Progress section. 

Choosing a tool instead of a conventional white board not only enables you quickly change the configuration of the board, but also track your progress in automatically drawn Burndown chart or measure such Kanban metrics as Lead or Cycle time.
 Check  Eylean website to find out more about this easy to use Kanban and Scrum tool. 




Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}