Kanban vs Scrum
AgileTune supports both Kanban and Scrum workflows. Choose the approach that fits your team's cadence, or switch between them at any time.
Overview
Both Kanban and Scrum are agile frameworks for managing work, but they differ in structure. Kanban emphasizes continuous flow while Scrum organizes work into fixed-length sprints.
Key Differences
| Aspect | Kanban | Scrum |
|---|---|---|
| Cadence | Continuous flow | Fixed-length sprints (1–4 weeks) |
| Planning | On-demand, pull-based | Sprint planning before each sprint |
| Roles | No prescribed roles | Product Owner, Scrum Master, Developers |
| WIP Limits | Per column | Per sprint (sprint backlog) |
| Metrics | Lead time, cycle time, throughput | Velocity, burndown chart |
| Changes | Can reprioritize at any time | Changes discouraged mid-sprint |
When to Use Kanban
- Your team handles ongoing work with unpredictable arrival (e.g., support, bugs)
- You want maximum flexibility to reprioritize at any time
- Work items vary significantly in size and complexity
- You're just getting started with agile and want a lightweight framework
When to Use Scrum
- Your team works on a product with planned feature releases
- You want regular delivery cadences and predictable velocity
- Stakeholders need visibility into what will be delivered and when
- The team benefits from structured ceremonies (standups, retros, planning)
Switching Between Modes
You can switch a project between Kanban and Scrum at any time without losing data:
- Go to Project Settings → Board
- Under Board Type, select Kanban or Scrum
- Click Save
When switching to Scrum, any existing tasks in your columns are preserved. You can then create your first sprint and move tasks into it. When switching to Kanban, active sprint tasks are moved back to the board columns.