Jira supports two main Agile board types — Scrum and Kanban — and choosing the right one depends on how your team plans and delivers work. Both boards visualize progress, but they operate on different rhythms.
How Scrum Boards Work
A Scrum board is built around fixed-length sprints, typically one to four weeks long. Teams plan a set amount of work at the start of the sprint, track it on the board during the sprint, and review completed work at the end, using velocity to plan future sprints.
How Kanban Boards Work
A Kanban board has no fixed sprints. Work flows continuously through columns, and teams often set work-in-progress limits to prevent overloading any single stage. This makes Kanban well suited for support teams and workflows where priorities shift frequently.
Scrum relies on sprint planning; Kanban relies on WIP limits
Scrum boards reset each sprint; Kanban boards stay persistent
Scrum suits planned feature work; Kanban suits ongoing support
Both boards can be customized with columns and swimlanes
Setting Up Each Board in Jira
Scrum board workflow
Create a project using the Scrum template, or add a Scrum board to an existing project.
Write and rank issues in the Backlog view, with the most important work at the top.
Click Create sprint, drag issues into it, set a goal and press Start sprint.
Track progress on the active sprint board during daily stand-ups.
Press Complete sprint at the end; unfinished issues move to the backlog or the next sprint.
Kanban board workflow
Create a project using the Kanban template.
Map columns to your real stages, such as To Do, In Progress, Review and Done.
Open board settings and set a maximum number of issues for busy columns. Jira highlights a column when it goes over its limit.
Pull the next item only when someone has capacity, rather than assigning everything up front.
Reports That Come With Each Board
Board
Main reports
What they tell you
Scrum
Burndown chart
Whether remaining work is falling fast enough to finish the sprint
Scrum
Velocity chart, sprint report
How much the team usually completes, and what was added or dropped mid-sprint
Kanban
Cumulative flow diagram
Where work is piling up; a widening band means a bottleneck
Kanban
Control chart
How long issues take from start to finish, and how predictable that is
Exact report names can vary slightly between company-managed and team-managed projects, but the ideas are the same: Scrum reports focus on the sprint, Kanban reports focus on flow and cycle time.
A Practical Example of Choosing
Consider one company with two teams. The product team builds a new mobile feature with clear scope, a demo for stakeholders every fortnight and a release plan. A Scrum board fits them: sprint planning sets a target, and the burndown shows early if the goal is at risk.
The support team handles customer bugs that arrive at any time, with urgent ones jumping the queue. Forcing these into a sprint would mean constant scope changes. A Kanban board with a WIP limit on "In Progress" lets them finish what they start and react to urgent tickets without breaking a plan.
Some teams mix the two, often called Scrumban: they keep regular planning and review meetings but run a continuous board with WIP limits instead of a fixed sprint commitment.
Mistakes and a Decision Checklist
Using a Scrum board but never closing sprints, which makes every report meaningless.
Running Kanban without WIP limits, so the board becomes a long list of half-done work.
Creating too many columns; each extra stage adds handovers and waiting time.
Switching board type every few weeks before the team has learned either one.
Choose Scrum if work can be planned for a short period, stakeholders expect regular demos and the team wants a shared goal. Choose Kanban if work arrives unpredictably, priorities change daily or the team mostly handles requests and maintenance. Either way, review the board together regularly and adjust columns as the process improves.
Master Jira with Expert-Led Training
Hands-on classes, mentor support, and placement assistance — all in one course.