0

1.3kviews

Scrum model vs. Kanban model

written 7.0 years ago by teamques10 ★ 70k

software engineering

ADD COMMENT FOLLOW SHARE EDIT

1 Answer

0

23views

written 7.0 years ago by teamques10 ★ 70k

Scrum	Kanban
Based on Agile values	Based on Lean values
Team is required to estimate work	your team is not required to estimate the tasks
Requires a change in current processes	Reuses your current processes and doesn't require a massive change in how your team works
velocity is a metric to determine when working software can be delivered to a customer or stakeholder	Lead time is a metric to determine when working software can be delivered to a customer or stake holder
Prescribes 3 roles-Scrum Master, Product Owner and members of the Delivery Team	Does not have specific or prescribed roles
Can use a Sprint burn down report to show the health of a spirit	May use a cumulative flow diagram to report progress
Priorities do not change during a sprint	Priorities can change daily
Great for new product or feature development	Better suited for tasks that are repetitive such as tasks that most would consider,"Business as Usual".
Requires a small, dedicated team	Team size is irrelevant
Bottlenecks are not always obvious until your Sprint Review or Retrospective	Bottlenecks are revealed quickly -through visualization

ADD COMMENT SHARE EDIT