Professional Documents
Culture Documents
Scrum or Kanban
Scrum or Kanban
Characteristics of Kanban
Kanban finds its origins in manufacturing and was developed by Toyota to improve manufacturing
efficiency, cutting back on waste (Kanban Tool, 2022).
A very apt definition of Kanban as given by Kanbanize (2023) states that “Kanban is a Lean workflow
management method for defining, managing, and improving services that deliver knowledge work. It
helps you visualize work, maximize efficiency, and improve continuously.” and it is optimally geared
to meet customer demand just in time rather than pushing goods to the market (Macwan, 2023). It
is particularly well suited for providing the optimum response to dynamic demands and
unpredictable work requirements. By virtue that kanban is a pull system (Kissflow Inc, 2022),
replacing completed work with new work to be done it enhances the workflow and allows for better,
quicker dealing with higher priority work whilst getting the best result with the resources available.
One of its main features is the visual representation of the work on, what is called, Kanban (kan =
sign, ban = board). Past, present and upcoming work is visualised and can easily be updated to show
what work is in progress or has been done as well identifying possible bottlenecks.
Characteristics of Scrum
Scrum had originally been conceived withing product development with a focus on teamwork as
driving force. It was not long before the principles were translated into use as project management
framework for software development.
Scrum can be defined as a framework for project management that emphasizes teamwork,
accountability and iterative progress toward a well-defined goal (Lutkevich, 2021). The technique
helps teams to deliver valued products iteratively and incrementally, while continually inspecting
and adapting the process. All the while the focus is on the empirical process and the use of regular,
typically short meetings in order to deliver the best value to the customer (Sliger, 2011).
The choice
Many are the similarities between the two techniques and so it seems no explicitly wrong choice can
be made, but a rationale can be applied as suggested by Kashyap (2022) which states:
Provided that the software in our scenario is an established, stable software the preference would
be given for the more steady-paced update cycle with set intervals of Scrum. This would allow for a
Daniel Lagerwaard 2023003268 MGT719 Discussion Activity 2 B
more stable development process and greater focus on human collaboration versus the more ad hoc
style of Kanban and provides easier planning of implementation.
References: