Who this board is for
Development teams of three to ten people working in sprints or Scrumban. Product owners keep upcoming work in Maybe?; the team pulls what it commits to into the sprint backlog at planning.
The columns, and what each one means
- Maybe?
- Every new card lands here first. Decide whether it is real work before it takes a slot on the board.
- Sprint backlog
- Committed for this sprint, not yet started.
- In progress
- Being built. One card per developer is a healthy limit.
- Code review
- Pull request open, waiting for review.
- QA
- Merged to staging, being tested.
- Done
- Close a card when it is finished. Closed cards keep their history and can be reopened.
- Not Now
- Cards nobody touches for 30 days (or the period you choose) move here on their own, so the board only shows live work.
How to run it
- Before planning, the product owner orders Maybe? so the most valuable ideas are on top.
- At sprint planning, move the cards you commit to into Sprint backlog. Break big stories into steps.
- Pull cards left to right. Nobody starts a new card while one of theirs is waiting in Code review.
- At the end of the sprint, close what shipped. Move unfinished cards back to Sprint backlog or Maybe?.
- Use the account activity timeline in your retrospective to see what actually happened.
Suggested tags
#story user-facing change#tech internal work, refactors, upgrades#spike time-boxed research#carry-over unfinished from last sprint
Tips from teams who use this board
- Set auto-postpone to 30 days so ideas the team never commits to quietly leave Maybe?.
- Use steps for sub-tasks; the “3/5” counter is a faster progress signal than burndown charts for small teams.
- If Code review is always full, that is the bottleneck. Swarm reviews before starting new work.