Build a Sprint Board in Linear (2026): A Step-by-Step Setup for Software Teams

Linear has quietly become the default issue tracker for product engineering teams that found Jira too heavy and Trello too light. Its speed is the headline, but the reason teams stay is the cycle model — Linear’s name for a sprint — which is opinionated in a way that removes a lot of the ceremony other tools impose.

This guide builds a sprint board from zero: a team, a cycle, a board view, and the automations that keep it honest. It assumes a team of 5–20 engineers. If you are coming from Jira, pair this with our Jira setup for software teams guide to map concepts; if you are choosing between the two, our Linear vs ClickUp comparison lays out the trade-offs.

TL;DR

Linear’s “cycle” is your sprint — enable it, set a fixed length (we recommend 2 weeks), and let it auto-start.
Build one Board view grouped by status; add a second Triage view for incoming requests.
Use status workflows (Backlog → Todo → In Progress → In Review → Done) and never let “In Progress” exceed your team’s parallel capacity.
Pricing: Free covers unlimited members; Basic $10/user/mo and Business $16/user/mo (yearly) unlock the team and automation features most squads need.
Keep specs in Notion or docs; Linear owns status, not narrative.

Why Linear for sprints

Linear is built around the assumption that most status meetings are a failure of tooling, not communication. Cycles auto-rollover, board views update in milliseconds, and the keyboard-first UX means an engineer files a ticket without leaving flow state.

Where it shines versus alternatives:

Speed — opening, filtering, and moving issues is instant. Jira’s click-lag is the common reason teams switch.
Cycles over sprints — Linear forces a rhythm (start date, end date, auto-progression) so unfinished work is visible, not hidden.
Triage queue — incoming requests sit in a review state until an owner accepts them, which stops the backlog from becoming a dumping ground.

Read our full Linear review for the deeper feature assessment.

Step 1: Create the team and choose a workflow

A “team” in Linear is the unit that owns issues and cycles. Create one per squad (e.g., “Web,” “Platform”). Do not create one mega-team for the whole org — you lose the per-squad cycle clarity.

Set the issue status workflow. The default (Backlog, Todo, In Progress, In Review, Done) is right for most teams. Add a “Canceled” state. Keep it to five or six states; more than that and people stop using them consistently.

Tip: name your workflow states to match how your team actually talks. If you say “in code review,” call the state “In Review,” not “Verification.”

Step 2: Enable and configure cycles

Go to the team settings → Cycles. Set:

Cycle length — 2 weeks is the safe default; 1 week if your work is very granular, 3 if you ship big chunks.
Auto-start new cycles — on. This removes the “who remembers to start the sprint?” problem.
Carry-over — allow unfinished issues to roll to the next cycle, but review them in the retro so they do not accumulate forever.
Current cycle in the sidebar — on, so the board is one click away.

Linear shows velocity (completed points per cycle) automatically once you use estimates. Do not over-invest in estimation early; start with a simple points field and refine after three cycles.

If your team is still learning agile mechanics, our Scrum/Kanban in Jira beginner guide explains the underlying ceremonies that map cleanly onto Linear cycles.

Step 3: Build the board view

Create a view called Board, grouped by Status. This is your sprint board. Add filters:

Cycle is Current — so the board only shows this sprint’s work.
Assignee is Anyone — so unassigned work is visible (and embarrassing, which is the point).

Add a second view, Triage, filtered to the Triage status, grouped by nothing. Route all incoming requests (from a Slack integration or the “Create issue” button) here. An owner reviews Triage daily; accepted issues get a status and an assignee, rejected ones get closed with a reason.

Step 4: Wire up automation

Linear’s automation is where the setup pays off:

Auto-assign — route issues by label to the right engineer or keep them in Triage.
Cycle rollover — unfinished In Progress issues can auto-move to the next cycle or stay; we keep them and review.
Slack notifications — post new Triage issues to a #intake channel so nothing hides.

On the Free plan automations are limited; Basic and above open the full set. For most squads the Basic tier is the real entry point.

Step 5: Connect specs without duplicating them

Do not write specs in Linear. Write them in Notion or your docs tool (see our Notion for software teams setup) and link the spec URL on the parent issue. Linear’s “parent” and “blocked by” relations handle dependency tracking; the prose lives elsewhere. This keeps Linear fast and your docs rich.

Our wider best PM software for dev teams 2026 guide ranks where Linear sits versus Jira, ClickUp, and GitHub Projects for engineering orgs.

Pricing you will actually pay

Linear is per-user, billed yearly on paid plans:

Free — $0, unlimited members, 2 teams, 250 issues (plenty for a small squad or a pilot).
Basic — $10 per user/mo (billed yearly); 5 teams, unlimited issues, admin roles.
Business — $16 per user/mo (billed yearly); unlimited teams, private teams, Triage Intelligence, code intelligence.
Enterprise — custom (SAML, SCIM, advanced security).

Verified against the Linear pricing page on 2026-09-12.

For a 10-engineer team, Basic runs $100/mo and covers cycles, board views, and core automations. Move to Business ($160/mo) when you need private teams, Triage Intelligence, or code-integration features. Compared with Jira’s Standard at $7.91/user/mo and Premium at $14.54/user/mo (our Jira review has the detail), Linear is marginally pricier at the low end but wins on speed and UX.

Team perspective: pick Linear if…

If your team is under 20 engineers and values speed and a clean cycle rhythm over enterprise workflow config, pick Linear (Basic, $10/user/mo) over Jira. You will ship faster and hold fewer status meetings. The trade-off: Linear is weaker at cross-project portfolio management and heavy compliance controls, so a 100-person org with audit requirements may still land on Jira or ClickUp. For everyone else, start on Linear Free, graduate to Basic at ~8 people, and only reconsider when you hit a ceiling Linear does not cover.

Verdict

A Linear sprint board takes under an hour to stand up and, because cycles are opinionated, it stays honest without a Scrum master policing it. Create the team, enable 2-week cycles, build a Board + Triage view, and link specs rather than rewriting them. Keep the tool doing what it is best at — tracking status fast — and your sprint rituals get lighter, not heavier.

How this content was prepared: This tutorial is based on Linear’s official documentation, publicly available pricing, and our team’s hands-on use of Linear for sprint tracking. It is not sponsored, and no vendor influenced the recommendations. Pricing is dated in the metadata above.