Kanban for Software Development Teams

Kanban for Software Development

Software teams benefit enormously from Kanban because it maps naturally onto the development lifecycle. Here is a proven column layout for engineering teams.

Recommended Column Layout

Backlog → Ready → Development → Code Review → QA → Staging → Done

Each column represents a stage in the software delivery pipeline:

• Backlog -- All future work items, roughly prioritized.
• Ready -- Items that are fully specified and ready for a developer to pull.
• Development -- Active coding work. WIP limit: 1-2 per developer.
• Code Review -- Pull requests awaiting peer review.
• QA -- Items under testing. May include automated and manual testing.
• Staging -- Deployed to a staging environment, awaiting final approval.
• Done -- Merged and deployed to production.

Color Labels for Software Teams

Use color labels to categorize card types:

• Red -- Bug / Production issue
• Blue -- Feature / User story
• Yellow -- Tech debt / Refactoring
• Green -- Documentation / Process improvement
• Purple -- Spike / Research

Pull Requests and Code Review

The transition from Development to Code Review is where many teams experience bottlenecks. Setting a WIP limit on Code Review (e.g., no more than 3 items) ensures reviews are completed before new work begins. This dramatically reduces cycle time.

Tips for Engineering Teams

• Keep cards small. A card should represent 1-3 days of work at most.
• Include acceptance criteria on every card.
• Use the description field for links to PRs, design docs, or tickets.
• Review blocked items daily in standup.