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:
Kanban
|
Scrum
|
|
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
|
|
Cycle time
|
Velocity
|
|
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.
No comments:
Post a Comment