SCRUM Vs Kanban

SCRUM Vs Kanban: The underlying principles of Kanban enable it to maximize delivery of value in shorter periods of time than traditional Agile. In this article, we look at SCRUM Vs Kaban and look at the primary differences between them.

Below are the FIVE basic characteristics of a Kanban implementation:

1. Visualize your workflow
2. Apply “Work in Progress” limits (a.k.a WIP limits)
3. Make policies explicit
4. Manage and measure flow
5. Optimize iteratively with data

Video: SCRUM Vs Kanban

SCRUM Vs Kanban: Differences

• SCRUM has Regular fixed-length sprints (example, 2 weeks as a best practice). Whereas Kanban works on continuous flow
• In SCRUM, we release an increment at the end of each sprint (if approved by the product owner). In Kanban, we have continuous delivery or at the team’s discretion
• In SCRUM, we have Roles such as Product Owner, Scrum Master, development team. Whereas in Kanban, there are no standard roles. Some teams enlist the help of an agile coach
• In SCRUM, Velocity is the key metric. In Kanban, Cycle time is the key metric
• In SCRUM, teams should strive NOT to make changes to the sprint forecast during the sprint. Whereas in Kanban, change can happen at any time.

Kanban Benefits

Here are some known benefits of Kanban listed:

• Planning flexibility
• Shortened time cycles
• Fewer bottlenecks
• Visual metrics
• Continuous Delivery

Conclusion

Though on the surface both SCRUM and Kanban look mutually exclusive, they can actually go hand in hand. While Kanban is very visual and stresses “focus” on work that is under escalation, SCRUM is prescriptive and has a cadence to synchronize with the market expectations on the product.