Haut de page

Jira Agile board: Scrum or Kanban?

Posted by

December 5, 2017

In  fast paced and ever-changing environments, more and more teams are using Agile methodologies to build and ship products that meet their customers expectations.

Since Jira version 7.x, Jira Agile has become Jira Software, which is a tool developed by Atlassian and designed to support Agile methodologies – both Scrum and Kanban – within Jira. It enables project teams who are already using Jira to adapt to Agile practices, the easy way. However, when configuring Jira Software, one big question arise: going Scrum or Kanban?

If you are not familiar with agility, this article will provide you insights on which board to choose in Jira Software, and help you make the right decision for your team.

Scrum vs Kanban

Scrum Boards

A Scrum boards is a board that was created using Scrum framework and is a board for teams who like to plan their work in detail before they can start a project. This usually includes creating sprints and giving story points to user stories in order to plan which story can go to each 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 Active sprint mode. The Plan mode, as explained above, includes moving issues from backlogs and giving each one a time estimate. The Active sprint mode is the actual “Kanban” board in itself, where you can move cards (issues) across columns (statuses). It also gives you the ability to Complete Sprints.

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 board uses the same column-based interface as Scrum Active sprint board for tracking the status of tasks, however without the ability to organize these into sprints. This board will deal with all the issues in the project rather than a portion of them.

In the recent version of Jira Core, users are able to create Kanban boards to track their tasks. You will not have all the features that come with the Kanban board in Jira Software.





This is where the team will plan sprints and estimate stories that will go into each sprint


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 Scrum team, the PO will sit with the developers and ask for their estimates. This information can be entered directly into Jira Software.


This is 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

Active Sprint Board

This is the Work mode (in Kanban), where you can see the board broken down into different statuses. This allows the team to see the progress of sprints


You can limit the minimum and maximum number of issues that should be displayed in each status. This will change the color and make it obvious for the team to decide to whether to increase or decrease the number of issues.


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.


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.


This board allows you to apply to most basic Kanban principles to improve the flow of stories.

Some criteria to help you make your decision

So how would you know which one is best for you? Well, there are simple things that you need to look out for:

Setting up speed

If you are looking to start working on a board quickly and with minimal configurations, then Kanban is the way forward. Other than creating new columns and mapping your statuses, Kanban requires very little configuration and enables users to get started pretty much instantly.

Detailed overview of the project

If you are looking for more detailed tracking of your project progress, then Scrum; with its planned sprints, story points,  and assortment of charts and reporting tools (Burndown Chart, Sprint Report, Epic Report, Velocity Chart, Version Report etc), is the best option for you.


Scrum allows a lot more functionalities than Kanban, simply because Scrum involves a lot more planning before you can actually begin to work on the issue. With Kanban it’s more straightforward, simply getting the issues on the board and mapping them to the correct status. Scrum also comes with more reporting capabilities than Kanban.

Ease of use

Scrum can be quite complex to set up due to the amount of planning involved. You have to add versions, story points, sprints, keep track of the issues that are in the backlog and in the sprint, issues that have been completed in the closed sprints etc. This can be too much to handle for some users, whereas with Kanban, you can see all the issues within a project on one board. Kanban is suitable for business teams who only care about their task management and where it is at every given point.

Project Size

This is also a very key aspect of the decision making. If you are working on a small scale project with only a limited number of issues, then Kanban is undoubtedly the simpler option. With a larger scale project however, with greater numbers of concurrent issues, developers, Scrum will offer greater organization, process management, and overview. Projects that follow Scrum framework will benefit highly from using the Scrum board.


Both Scrum and Kanban methodologies are great, but they are no one size fits all. Making the right decision for your team at the very start can save from the burden of carrying complex changes in workflows and habits.

We’d love to hear from you: what choice criteria is the most important according to you? Let us know in the comment section! If you’re still not exactly sure, click below to get in touch with one of our certified Atlassian consultants.