Scrum & Kanban in Jira for Beginners: Set Up Your First Board and Sprint (2026)

TL;DR

Jira is the default issue tracker for software and Agile teams because its boards, backlogs, and sprints are purpose-built — not bolted on. This guide gets a beginner productive in one sitting: pick a Scrum or Kanban template, build a backlog, and start moving work across the board. Start on the Free plan (up to 10 users); you only pay when you need AI features, advanced roadmaps, or 24/7 support. If your team isn’t writing software, a simpler tool is usually the better fit — see our best project management software 2026 overview to compare first.

Scrum vs. Kanban in Jira (pick one, don’t mix)

Both run on the same engine, but they answer different questions:

• Scrum = time-boxed sprints (usually 2 weeks), a prioritized backlog, and a commitment for the sprint. Use it when work arrives in planned chunks and you want predictability.
• Kanban = continuous flow, a board with columns, and a work-in-progress (WIP) limit. Use it when work is interrupt-driven (support, ops, bug triage).

The most common beginner mistake is turning on Scrum “because Agile” and then ignoring sprints. If you won’t plan two-week commitments, pick Kanban — it’s honest about how you actually work. Our Jira review covers where each template shines in more depth.

Team perspective: when Jira is the right call

If you’re a team under 10 people shipping software, Jira beats Trello and ClickUp for one reason: story points, sprint velocity, and epics are native, not faked with labels. You graduate to Jira the moment “a task” needs to become “a story with acceptance criteria, part of an epic, estimated in points.” A content or ops team of the same size should usually stay on Trello or ClickUp — Jira’s power is also its weight, and you pay for it in onboarding time.

The exception is a cross-functional team where engineering drives the plan and marketing/ops just watch. Give non-devs view-only or a simplified board; don’t force them into sprint ceremonies.

Step 1 — Create the project and choose a template

1. Log in to atlassian.com/software/jira and click Create project.
2. Under Software, pick Scrum or Kanban. (Use Business only if you have no dev workflow; the Agile templates are what this guide covers.)
3. Name it after the team or product — “Payments Squad,” not “Project Alpha.”
4. Choose Team-managed for a self-contained board you control, or Company-managed if an admin owns shared workflows. Beginners: Team-managed keeps you out of admin politics.

Step 2 — Build the backlog (Scrum) or the board (Kanban)

Scrum: open the Backlog tab. Click + Create and write real items:

• An Epic is a big initiative (“Checkout redesign”).
• A Story is a deliverable (“Add 3-DSecure step to payment form”), estimated in points.
• A Task or Subtask is the grunt work.

Kanban: the board opens with To Do / In Progress / Done. Add a Blocked column if work frequently waits on someone else.

Write specific actions, not topics. “Fix timeout on retry” beats “Retries.”

Step 3 — Run your first sprint (Scrum)

1. On the Backlog, select the top stories you can finish in two weeks and click Create sprint.
2. Drag them into the new sprint.
3. Click Start sprint, set the end date (default 2 weeks), and start.
4. Each day, move a card to In Progress → Done as state changes. The board is your standup — no meeting required.
5. At the end, click Complete sprint; unfinished cards fall back to the backlog.

Velocity (points finished per sprint) becomes your planning compass after three sprints. Don’t estimate in hours on day one — points are deliberately fuzzy so the team calibrates over time.

Step 4 — Workflow, columns, and WIP limits (Kanban)

1. Open the board settings → Columns. Keep it to 3–5: To Do / In Progress / Review / Done.
2. Set a WIP limit on In Progress (e.g., 3) so the team finishes before starting more. A ballooning In Progress is a signal you committed to too much, not a reason to add a tool.
3. Add a Done rule so finished work auto-archives weekly.

Step 5 — Use epics and the Timeline view to see the big picture

Once you have more than one sprint’s worth of work:

• Group stories under an Epic so leadership sees progress by initiative, not by card.
• Open Timeline (Premium) to spot dependencies — card B can’t start until card A ships.

On the Free and Standard plans you still get Board, List, Calendar, and Summary views, which is enough for most small teams. The Timeline/advanced roadmaps are the main reason to step up to Premium.

2026 Jira pricing reality (verified)

Jira bills per user. The public plans are:

Plan	Price	Seats included	What matters for beginners
Free	$0	Up to 10 users	Unlimited projects/tasks, boards, 150 automation steps/mo, 2 GB storage
Standard	$7.91/user/mo (billed annually)	Up to 100,000/site	Rovo AI search, user roles, 250 GB storage, 9/5 support
Premium	$14.54/user/mo (billed annually)	Up to 100,000/site	Cross-team roadmaps, dependency management, 24/7 critical support, 99.9% uptime SLA
Enterprise	Contact sales	Custom	Advanced admin, multiple sites, 99.95% SLA

Verified against Atlassian’s Jira pricing page on 2026-09-02.

Two things beginners miss:

• The Free plan is enough for a first team. You only need Standard when you exceed 10 users or want Rovo AI; you need Premium when you manage dependencies across teams or require an uptime SLA. A 5-person squad can stay Free for months.
• Enterprise is quote-only. If a sales rep won’t name a number, you’re not its customer yet — Standard or Premium covers the vast majority of teams.

Team perspective: Standard vs. Premium for a small team

If you’re under 10 people and not running cross-team programs, Standard at $7.91/user/mo is the sweet spot — you get roles, more storage, and AI search without paying for roadmaps you won’t open. Step up to Premium at $14.54/user/mo only when you actually manage dependencies between squads or your contract demands an uptime SLA. Paying for Premium on day one is the classic “buy the Ferrari to drive to the corner store” move. For the full feature trade-off against other tools, see our best PM software for software dev teams guide.

Common beginner mistakes

• Scrum without sprints. If you never start/complete a sprint, you’re on Kanban with extra steps. Switch the template.
• Estimating in hours. Points self-calibrate; hours invite false precision and arguments.
• Too many columns. Five max. More places for a card to hide means the board lies.
• No epic hierarchy. A flat backlog of 200 cards is unplannable. Group under epics early.
• Forcing non-devs into ceremonies. Give them a view-only board and a weekly summary instead.

Bottom line

A beginner can stand up a working Jira board in one sitting: create a Scrum or Kanban project, write specific stories or cards, and start moving work across the board daily. Resist every “advanced” feature — epics, Timeline, automation — until a real need appears. Jira’s value is that it speaks Agile natively; the moment it feels heavy, that weight is telling you your team may not be an Agile team yet. Start on Free, earn the paid tiers, and graduate only when the workflow demands it.

---

How this content was prepared

Transparency note: This article is based on each vendor’s official documentation, publicly available pricing and feature information, and our editorial analysis. It is not sponsored, and no vendor paid for or influenced the recommendations.

We do not claim to have independently tested every tool end-to-end. Where a verdict reflects operator judgment, it draws on public documentation and editorial analysis, not comparative hands-on trials. Pricing and feature details are dated in the metadata above.