This post will focus on Kanban vs SCRUM. There are many similarities between Kanban and SCRUM. These are as follows:
· Both are Lean and Agile
· Both use pull scheduling
· Both limit WIP
· Both use transparency to drive process improvement
· Both focus on delivering releasable software early and often
· Both are based on self-organizing teams
· Both require breaking the work into pieces
· In both, release plan is continuously optimized based on empirical data (velocity / lead time)
They are differentiated by the rules for the development team as to how they should work on a project. The Scrum process is quite prescriptive while Kanban is more open and this difference is visible from the rules of scrum and kanban, which are as follows:
- The product owner organizes and managers the product backlog.
- There are cross-functional teams
- Once a sprint has been created, the tickets (tasks decided) cannot be changed or interrupted.
- Each sprint is time bound, usually 2 weeks depending on the team and project.
- Everyday, there should be a daily scrum meeting where every team member has to answer three questions, what was done yesterday, what will be done today and lastly, were there any roadblocks to accomplish yesterday’s task.
- Burn-down charts are used to measure the progress of the sprint.
- At the end of each sprint, a demo is given to the stakeholders by the team.
Kanban is comparatively much flexible and it has two rules only making it open.
- Workflow is has to be visualized before work is started.
- Work in progress is limited to a number of tasks.