Summary -
In this topic, we described about the below sections -
What is Scrum?
Process of Agile which focuses on delivering the Business value in shortest period of time. It focuses on accountability, teamwork, and iterative progress towards a goal.
What is Kanban?
Kanban is a kind of dashboard called as ‘Kanban Board'. It displays the workflow of tasks. It is a method used to manage, define, and improve services for delivering knowledge. Team members can see the progress of work at every stage of development.
Differences
| SCRUM | KANBAN |
|---|---|
| Planning is a first priority in Scrum. It starts with sprint planning and ends with sprint Retrospective. | Kanban is less rigid, and things keep changing dynamically. |
| Collection of time measurements made during sprints. | Graphs are used for drawing out an overview of team's progress overtime. |
| Depends on sprint goals and forecasts. | Depends on time boxing and forecasts. |
| As it stresses on Planning, Estimation has a particularly important role in scrum. | There will not be any mandatory requirements for estimation. |
| Every individual has their own responsibilities and roles. | There will not be any set of roles and responsibilities. |
| Duration of every iteration varies from 2 weeks to 1 month. | This is measured during cycle times. |
| Required to commit a specific amount of work. | Not necessary for any commitment. |
| Cross Functional teams are important because, if there is any bottleneck in the system it can be resolved in a team quickly and easily. | Specific teams are important. |
| Scrum helps to save time and money. | Kanban focuses on productivity, efficiency, and continuous improvement. |
| Here, Scrum master plays an important role in solving any issues. | Every team member has their own responsibilities. |
| Work is done batch/sprint wise. | It works on the movement of Single-threaded work item flows. |
| Total cost of the project is minimal which may lead to quicker and cheaper result. | Total cost of the project will never be accurate. |
| It is easy to deliver a quality product at a scheduled time. | Regular, steady output and any major changes in customer demand may make Kanban go down. |
| Large projects can be easily divided into sprints. | Not suitable for large size teams. It works well for small teams. |
| The Project plan would never be disturbed even when the team members leave. | If any of the team members leaves the team, then the project development would be disturbed. |
| Using this method, a quality product can be delivered at a scheduled time. | This is designed for a regular, steady output. Major changes from customer would make the Kanban fail. |
| Stable and consistent performance at all the levels. | Goal accomplishment would be easier due to the visual nature of Kanban. |
| Scrum would require a complete change from traditional model to Agile scrum model that would be implemented in the project. | Drastic changes are not allowed in Kanban projects. |