Skip to content
Projects Strategy Community

Kanban & Agile Scrum: Is the Basic Concept Similar?

There are some Six core practices available in Kanban, let us discuss one by one in similarity with Scrum concepts:

1) Visualize the workflow

In Kanban, Visualising the flow of work and making it visible is key to understanding how work proceeds. In Kanban we are doing this using card wall.
In Agile scrum we are also using Scrum wall to show list of user stories and their progress. In Sprint planning meeting and Daily Standup meeting we visualize, how the sprint will progress.

2) Limit WIP

In Kanban, Limiting WIP is to implement a pull system where software is developed incrementally based on the available capacity of the team.

Similarly in agile Scrum, Scrum master manages the team capacity and based on the available capacity, team members takes ownership for the available tasks and develops the software accordingly.

3) Manage Flow

In Kanban, The flow of work through each state should be monitored, measured and reported.

Similarly in Scrum, for every sprint we are keeping track of Sprint progress by burn down chart and reporting the sprint progress in Scrum of Scrums.

4) Make policies explicit

In Kanban, Without an explicit understanding of how things work and how work is actually done, any discussion of problems tends to be emotional, anecdotal and subjective (AKA a knee-jerk reaction).When team discusses the features which will be developed, they are more clear and can come up with good ideas.

In Scrum, in the sprint planning meeting Product Owner discusses the functionality and in the estimation meeting team gives the probable estimates of the feature, which needs to be developed.

5) Implement feedback loops

Both Scrum and Kanban implements feedback provided through customers or end users.

6) Improve collaboratively, evolve experimentally

Both Scrum and Kanban support the continuous improvement approach. Teams are working collaboratively, using their positives to help each other. Scrum is implementing continuous improvement through Sprint Retrospective meetings feedback and by making team members cross functional.

Not subscribed yet? Do it NOW! 

Author: Manoj Sharma (All Rights Reserved by the author).
Source: Original text (based upon first hand knowledge).
Image: © Yuri Arcus –
Help us to improve it: how-to, discussion.