Kanban is a method for managing the creation of products with an emphasis on continual delivery while not overburdening the development team. Like scrum, Kanban is a process designed to help teams work together more effectively.
Kanban is based on 3 basic principles:
Kanban promotes continuous collaboration and encourages active, ongoing learning and improving by defining the best possible team workflow.
Both Kanban and Scrum focus on releasing software early and often. Both require highly-collaborative and self-managed teams. There are, however, differences between the approaches:
|No prescribed roles||Pre-defined roles of Scrum master, Product owner and team member|
|Continuous Delivery||Timeboxed sprints|
|Work is ‘pulled’ through the system (single piece flow)||Work is ‘pulled’ through the system in batches (the sprint backlog)|
|Changes can be made at any time||No changes allowed mid-sprint|
|More appropriate in operational environments with a high degree of variability in priority||More appropriate in situations where work can be prioritized in batches that can be left alone|
Organization, culture and team dynamics often determine which method is the best fit.
Kanban and Scrum at their core are summarized by the premise: Stop Starting, Start Finishing. The entire team’s focus is on ‘getting to done’ for the tasks in progress.
VersionOne supports multiple teams using multiple agile methodologies. Teams use VersionOne to track the status of their items, setting WIP limits for each process stage to help them identify, manage, and mitigate constraints with the goal of optimizing the team’s flow.
Teams interested in Kanban benefit from VersionOne’s customizable Kanban board and collaboration capabilities.
If your Kanban teams are:
have a look at VersionOne.