Skip to content

// Sprint Board

Plan sprints, ship on time.

Kanban flow meets sprint discipline. Scope your sprint, track progress through columns, and ship every iteration with confidence.

// Board Preview
05 columns

Backlog

3

Redesign settings page navigation

Feature

Add bulk-edit support for card labels

Feature

Fix pagination offset on search results

Bug

Sprint Scope

2

Build webhook delivery retry logic

FeaturePriority

Migrate user avatars to CDN

Feature

In Progress

2

Implement role-based dashboard widgets

Feature

Patch XSS vulnerability in markdown renderer

BugPriority

Review

1

Add OpenTelemetry tracing to API gateway

Feature

Done

2

Ship two-factor authentication flow

Feature

Resolve race condition in invitation acceptance

Bug
// How to use this template
04 steps
01

Groom the backlog before sprint planning

Review backlog cards and estimate effort before pulling them into Sprint Scope. Cards without clear acceptance criteria stay in the backlog until refined.

02

Lock the sprint scope

Once planning is done, the Sprint Scope column is the commitment. Avoid adding cards mid-sprint unless something is truly urgent. Scope creep kills velocity.

03

Move cards through Review before Done

Every card passes through Review before reaching Done. This is where code review, QA, or stakeholder sign-off happens. No card skips review.

04

Run a retro at sprint end

After each sprint, look at what shipped versus what was scoped. Archive the Done column, move unfinished cards back to Backlog, and start fresh.

// FAQ
03 questions
01

How long should a sprint be?

+

Most teams run one- or two-week sprints. Shorter sprints give faster feedback loops but require more planning overhead. Start with two weeks and adjust based on your team cadence.

02

Can I combine kanban and sprints?

+

Yes, this template does exactly that. You get the visual flow of kanban with the time-boxed commitment of sprints. Cards flow through columns within a fixed sprint window.

03

How do I handle bugs during a sprint?

+

Critical bugs go directly into Sprint Scope and displace the lowest-priority scoped card. Non-critical bugs go to Backlog for the next sprint. Label them with Bug and Priority to track severity.

// Sprint starts now

Scope it. Ship it.

No credit card. Free sprint boards with real-time sync and drag-and-drop.