Scrum vs Kanban

Scrum vs Kanban

SCRUM BOARDS

Scrum boards are for teams who like to plan their work in detail before they start a project. This usually includes creating sprints and giving story points to user stories in order to plan which story can go to which sprint. When you first create a Scrum board, you create a list of items which becomes the backlog. From there, you create different versions and sprints and move the issue from backlogs to sprints.

Scrum boards have a Plan mode and a Work mode. The Plan mode, as explained above, includes moving issues from backlogs and giving each one a time estimate. The Work mode is the actual board itself, where you can move cards (issues) across columns (statuses).

KANBAN BOARDS

Kanban by contrast allows users to start work without necessarily having a structured plan, and in fact does not even have a plan mode. The Kanban work board uses the same column-based interface as Scrum for tracking the status of tasks, however without the ability to organize these into sprints. This board will deal will all the issues in the project rather than a portion of them.

Comparison

Scrum	Kanban
Backlog This is where the team will plan sprints and estimate stories that will go into each sprint	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.
Sprint Planning Usually when planning sprints in a PMO department, the BA and the PM will sit with the developers and ask for their estimates. This information can be entered directly into JIRA Agile.	Swimlanes This are a very good tool for separating and organizing issues. One example can be to separate issues by assignees. This way you can see how many issues have been assigned to each developer
Agile Board This is the Work mode, where you can see the board itself broken down into different statuses. This allows the team to see the progress of sprints	Constraints You can limit the minimum and maximum number of issues that should be displayed in each status. This will change the colour and make it obvious for the team to decide to whether to increase or decrese the number of issues.
Reports With Scrum boards, you can see many types of reports even while you are in the middle of the sprint. Burndown Chart – check the team progress towards their commitment. If the scope has 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	Reports Kanban also allows teams to view reports. One chart that is quite useful with Kanban is the Control Chart.This will allow you to measure the cycle time for issues. For example, showing the mean time and actual time taken to complete issues.
Scrum+Kanban This board allows you to apply to most basic Kanban principles to improve the flow of stories.