summaryrefslogtreecommitdiff
path: root/doc/en_US/kanban-vs-todo-and-scrum.markdown
blob: ea97811cbde13020afe186f0dd9c2b44387f5858 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
Kanban vs Todo lists and Scrum
==============================

Kanban vs Todo lists
--------------------

### Todo lists:

- Single phase (just a list of items)
- Multitasking possible (not efficient)

### Kanban:

- Multiple phases, each column represents a step
- Bring focus and avoid multitasking by setting a work-in-progress limit per column

Kanban vs Scrum
---------------

### Scrum:

- Sprints are time-boxed, usually 2 or 4 weeks
- Do not allow changes during the iteration
- Estimation is required
- Uses velocity as default metric
- Scrum board is cleared between sprints
- Scrum has pre-defined roles like scrum master, product owners and the team
- A lot of meetings: planning, backlogs grooming, daily stand-up, retrospective

### Kanban:

- Continuous flow
- Changes can be made at any time
- Estimation is optional
- Use lead and cycle time to measure performance
- Kanban board is persistent
- Kanban doesn't impose strict constraints or meetings; process is more flexible