Kanban

1. Kanban activities are continuous and more fluid.

2. Kanban is more visual, limiting the work in progress and maximizing efficiency
3. Kanban focus on reducing the time to complete a project
4. Kanban uses a user story and continuously improving the flow of work
5. Kanban has continuous delivery
6. Change can happen anytime in kanban

Scrum

 Scrum is more structured and based on short work intervals called sprints
 Scrum focuses on integrating customer feedback
 Scrum teams adopt specific roles like product owner, development team and scrum master
 Teams should not make changes during the sprint.

Kanban Board vs Scrum Board

Category Scrum Kanban

Planning When a ticket is created it will initially
go into the backlog. From the backlog, it
can be estimated and details can be
added before it goes into a sprint and
appear under Active Sprints.
Board View Scrum boards show the work that a
team has committed to under a specific
time-frame. This work will show as
sprints and progress is measured by
how much work that will be completed
within each sprint.
Workflow The statuses of the workflows
associated with the Scrum boards will
determine which columns can be
displayed. In order to change the
columns, the workflows have to be
changed.
With Scrum boards, you can see many
types of reports even while you are in
the middle of the sprint.
Reports An example is the Burndown Chart –
check how the team progress towards
their commitment. If the scope has
Any issue that is added to a Kanban board
will by default automatically fall into the
backlog column. There is also an option to
enable a Kanban backlog which is not
enabled by default.
Kanban boards shows all the work a
team has commited to but can be
configured to only display e.g. the most
recently added issues. Progress is
measured by looking at how many issues
are within each column, and restrictions
can be applied to only allow e.g. 3 issues
in progress at the same time
With Kanban boards it is a easier to
change your workflow. You can map
columns to the statuses of your workflow.
This can also be changed in the future if
the workflow changes, by simply adding or
removing columns as required.
Kanban also allows teams to view reports.
One chart that is quite useful with Kanban
is the Control Chart. This will allow you to
 changed while the sprint is still on, this
will also be reflected here. Other charts
include: Sprint Report, Epic Report,
Velocity Chart, Version Report, etc.
Maintenance Scrum boards allows you gain full
control and plan your work in great
detail, but it requires more configuration
time if any changes needs to be done
measure the cycle time for issues. For
example, showing the mean time and
actual time taken to complete issues.
Since Kanban boards don’t work with
estimates in the same way as Scrum
boards and are more simple to manage,
Kanban boards requires less maintenance