01
Scope the release before writing code
List every feature, fix, and breaking change in the Scoping column. Get sign-off from product and engineering leads before moving anything to Development. Scope clarity prevents last-minute cuts.
// Release Planning
From scope to shipped.
Track every feature and fix through five release stages. See exactly what is in QA, what is on staging, and what has shipped. No spreadsheets, no guessing.
Scoping
2Define v3.2 release scope with product team
Priority
Write API deprecation notice for /v1 endpoints
Feature
Development
3Build granular permission system for team roles
Feature
Add webhook signature verification
FeaturePriority
Fix date picker regression in card detail modal
Bug
QA
2Run load test on new search indexer
Feature
Verify backward compatibility of API v2 changes
Priority
Staging
1Deploy v3.1.1 hotfix to staging environment
BugPriority
Released
2Ship v3.1 with multi-board view and SSE improvements
Feature
Release mobile-responsive board layout
Feature
02
Track development progress per feature
Each card in Development represents one shippable unit. Use checklists for sub-tasks within a card. When the feature is code-complete and passing CI, move it to QA.
03
Gate releases through QA and Staging
QA validates correctness. Staging validates deployment. No card reaches Released without passing both gates. This catches integration issues before customers do.
04
Tag the release and archive the board
When all cards reach Released, tag the release in your repository, publish release notes, and archive the Done column. Start a fresh board for the next release cycle.
01 How do I plan a release with kanban?
+
Create columns for each release phase: Scoping, Development, QA, Staging, and Released. Add one card per feature or fix. Cards move left to right as they pass each gate. The board shows release readiness at a glance.
02 Should I create a new board for each release?
+
For major releases, yes. A fresh board keeps the scope clean and lets you archive the entire release as a historical record. For patch releases, add cards to an existing board with a version label.
03 How do I handle hotfixes during a release?
+
Hotfixes skip Scoping and go directly to Development with a Bug and Priority label. They follow the same QA and Staging gates but are prioritized above feature work. Track them on the current release board.
// Ship with confidence
Plan the release. Hit the date.
No credit card. Free release boards with real-time sync and full activity history.