JIRA Scrum Board
The Scrum Board in JIRA gives development teams a real-time, visual view of all work happening in the current sprint. Every issue appears as a card on the board. Cards move across columns from left to right as work progresses. The board replaces the need for status meetings because everyone on the team can see the current state of the sprint at a glance. This topic explains the board's structure, features, and how teams use it effectively during a sprint.
What Is a Scrum Board?
A Scrum Board is a digital version of a physical kanban wall used in Agile teams. In Scrum methodology, a team works in fixed time periods called sprints (typically 2 weeks). The Scrum Board displays all the issues committed to the current sprint and shows which status each issue is in.
Analogy: A Scrum Board works like a laundry room with three baskets labeled "Dirty Clothes," "In Washing Machine," and "Folded and Put Away." Each piece of clothing is a task. The goal is to move everything from the first basket to the last by the end of the week (sprint).
Scrum Board Layout
| Column: TO DO | Column: IN PROGRESS | Column: DONE |
|---|---|---|
|
MBA-42: Build OTP screen (5pts) MBA-43: Design login button (3pts) MBA-50: Add profile photo upload (2pts) |
MBA-38: Implement payment API (8pts) — Rahul MBA-40: Fix session timeout bug (3pts) — Vikram |
MBA-35: Create registration screen (5pts) MBA-36: Connect email verification API (5pts) |
Each card on the board shows the issue ID, a short summary, the assignee avatar, and the story points. Clicking a card opens the full issue detail without leaving the board.
Board Header — Sprint Overview
At the top of the Scrum Board, JIRA displays a sprint summary bar. This bar shows critical information about the active sprint at a glance.
| Element | What It Shows |
|---|---|
| Sprint Name | The name of the current sprint (e.g., "Sprint 5 — Auth Module") |
| Sprint Dates | Start date and end date of the sprint |
| Days Remaining | Number of calendar days left before the sprint ends |
| Issues Summary | Count of issues in each status (e.g., 5 To Do, 3 In Progress, 8 Done) |
| Complete Sprint Button | Available to Scrum Masters to close the sprint when work is finished |
Board Columns and Their Meaning
Each column on the board maps to one or more workflow statuses. The board administrator configures this mapping in the board settings. The columns represent the stages of work in the sprint cycle.
| Board Column | Mapped Workflow Statuses | Card Count Goal |
|---|---|---|
| To Do | To Do, Open, Reopened | Decreases during the sprint |
| In Progress | In Progress, In Review, In Development | Stays manageable (WIP limit applies) |
| Done | Done, Closed, Resolved | Increases during the sprint |
Work In Progress (WIP) Limits
WIP limits restrict how many issues can sit in a column at the same time. This forces the team to finish existing work before starting new work. Without WIP limits, developers often start many tasks simultaneously and finish none of them by sprint end.
| Column | WIP Limit | Rationale |
|---|---|---|
| To Do | No limit | All sprint issues start here — no restriction needed |
| In Progress | 4 (one per developer) | Each developer works on one issue at a time |
| In Review | 3 | Prevents a review bottleneck from building up |
| Done | No limit | No restriction on completed work |
When a column exceeds its WIP limit, JIRA highlights it in orange or red depending on the board theme. This visual signal tells the team to stop pulling new work and focus on clearing the bottleneck.
Board Filters and Swimlanes
Filters and swimlanes help teams view specific subsets of issues on the board without switching screens.
Board Quick Filters
Quick filters appear at the top of the board as clickable buttons. Clicking a filter instantly hides all cards that do not match the criteria. Multiple filters can be active at once.
| Filter | What It Shows |
|---|---|
| Only My Issues | Issues assigned to the logged-in user only |
| Recently Updated | Issues updated within the last day |
| Unassigned | Issues with no assignee — helps identify unclaimed work |
| High Priority | Issues with High or Highest priority |
Swimlanes
Swimlanes add horizontal groupings to the board. They allow the team to see cards organized by a dimension other than status. Common swimlane options include:
| Swimlane Type | Groups Cards By | Best For |
|---|---|---|
| Assignee | Each row shows one team member's issues | Tracking individual workloads |
| Epic | Each row shows issues from one epic | Tracking feature-level progress |
| Story | Parent stories in one row, their sub-tasks below | Seeing parent-child relationships |
| Expedite | High-priority issues in a separate top row | Highlighting urgent work |
| No Swimlane | All cards in a flat single list per column | Simple, small teams |
Daily Scrum and the Board
The Scrum Board is the centerpiece of the Daily Scrum (also called the Daily Stand-up). Each team member looks at the board and answers three questions:
| Question | Board Action |
|---|---|
| What did I complete yesterday? | Point to cards that moved to Done |
| What will I work on today? | Point to the card being picked up from To Do |
| What is blocking my progress? | Flag blocked cards on the board and raise the blocker |
Flagging an Issue
Flagging marks an issue as an impediment or blocker. A flagged card appears with a red or orange highlight on the board — immediately visible to the entire team and the Scrum Master. To flag an issue, right-click the card on the board and select "Add Flag." Flags do not change the issue status but signal that the issue needs attention.
Board Configuration
The board administrator customizes the board through Board Settings. Access Board Settings via the three-dot menu on the board header.
| Setting | What It Controls |
|---|---|
| Columns | Add, rename, or remove columns. Map workflow statuses to each column. |
| Swimlanes | Choose swimlane type (Assignee, Epic, Story, or none) |
| Quick Filters | Create or remove quick filter buttons using JQL |
| Card Layout | Choose up to 3 extra fields to display on each card (e.g., Priority, Due Date) |
| Card Colors | Color-code cards by Priority, Assignee, Issue Type, or custom JQL |
| Working Days | Set which days of the week count as working days for the burndown chart |
Completing a Sprint
At the end of the sprint, the Scrum Master clicks the "Complete Sprint" button. JIRA presents a summary of the sprint's completed and incomplete issues.
| Issue State at Sprint End | What JIRA Asks | Typical Action |
|---|---|---|
| Issues in Done | Nothing — they are archived with the sprint | Marked as completed in the sprint |
| Issues in To Do or In Progress | Move to Backlog or move to next sprint? | Carry over to next sprint if still needed |
Scrum Board vs Kanban Board
| Aspect | Scrum Board | Kanban Board |
|---|---|---|
| Work cycle | Fixed-length sprints (1–4 weeks) | Continuous flow — no sprints |
| Issue source | Sprint backlog (pre-committed set) | Backlog or queue (pulled as capacity allows) |
| Planning | Sprint Planning session before each sprint | No formal planning ceremony — pull when ready |
| Reports | Burndown chart, Velocity chart | Cumulative Flow Diagram, Cycle Time |
| Best for | Product development with fixed release cycles | Support, maintenance, and operations teams |
Summary
The JIRA Scrum Board gives teams a transparent, real-time view of sprint progress. Columns show the workflow stages. Cards represent issues. Swimlanes organize cards by epic, assignee, or priority. WIP limits prevent overloading. Quick filters focus attention on specific subsets of work. Flags highlight blockers. Daily stand-ups use the board as the single source of truth. Sprint completion cleanly archives finished work and moves unfinished items to the next sprint or backlog. Understanding the Scrum Board prepares learners to explore its counterpart — the JIRA Kanban Board — which serves teams with continuous, flow-based delivery needs.