73 / 104
73
Expert View
· Uzman Gözüyle
WHAT ARE THE DIFFERENCES BETWEEN
SCRUM AND KANBAN?
SCRUM
KANBAN
• Development starts and ends within the
allotted time period. (Sprint)
• Meetings are held for planning, process
improvements and delivery.
• The team promises to finish a certain
amount of work within a certain period of
time.
• Team’s speed is used as basic metric for
planning and process improvement.
• As a rule, development teams are required
to be cross-functional.
• Task items should be divided into smaller
parts to be completed within the Sprint.
• Use of Burndown graphs is recommended.
• Number of tasks developed will be limited
indirectly.
• Main rule is to make forecasts about task
sizes.
• No new task can be added to a Sprint in
progress.
• Sprint task list has to be owned by a
certain team.
• 3 roles would be determined. Product
owner, development team and scrum
master.
• Scrum Board would be recreated for every
new Sprint.
• Development continues non-stop.
Limiting is optional.
• Actions would be taken based on the
developments. There are no predetermined
meetings. It is optional to arrange
meetings.
• Promising is optional.
• Lead time is the main metric for planning
and process improvement.
• It is optional to have cross-functional
development teams. Teams where
expertise is at the forefront can be formed.
• Task item sizes may vary. There is no
indicated lower or upper limit.
• There is no requirement for using a certain
type of graphics. Any graph type can be
used.
• Number of tasks developed would be
limited directly. Work flow status would be
taken into account when limiting number
of tasks.
• It is optional to make forecasts about task
sizes.
• New tasks can be added as long as there is
sufficient capacity.
• Kanban board can be used multiple teams
or individuals.
• No specific role is defined.
• Kanban board is permanent.
How is Kanban Implemented at SBM?
First a Kanban teamwas formed and the teamwas informed about Kanban. In the next phase, tasks
are determined with weekly meetings and when tasks are completed, the outcomes are shared with
the managers during these meetings. The tasks to be included on the Kanban Board would be limited in
number based on the sizes of task items and when the incoming task load exceeds the limit, tasks are sent
back to the board to stay within the predetermined task limit. When there is sufficient capacity, a dynamic
work environment is provided by obtaining new outcomes with new tasks without staying idle.