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.
// Sprint Board
Kanban flow meets sprint discipline. Scope your sprint, track progress through columns, and ship every iteration with confidence.
Backlog
3Redesign settings page navigation
Add bulk-edit support for card labels
Fix pagination offset on search results
Sprint Scope
2Build webhook delivery retry logic
Migrate user avatars to CDN
In Progress
2Implement role-based dashboard widgets
Patch XSS vulnerability in markdown renderer
Review
1Add OpenTelemetry tracing to API gateway
Done
2Ship two-factor authentication flow
Resolve race condition in invitation acceptance
Review backlog cards and estimate effort before pulling them into Sprint Scope. Cards without clear acceptance criteria stay in the backlog until refined.
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.
Every card passes through Review before reaching Done. This is where code review, QA, or stakeholder sign-off happens. No card skips review.
After each sprint, look at what shipped versus what was scoped. Archive the Done column, move unfinished cards back to Backlog, and start fresh.
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.
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.
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
No credit card. Free sprint boards with real-time sync and drag-and-drop.