summaryrefslogtreecommitdiff
path: root/doc/kanban-vs-todo-and-scrum.markdown
diff options
context:
space:
mode:
Diffstat (limited to 'doc/kanban-vs-todo-and-scrum.markdown')
-rw-r--r--doc/kanban-vs-todo-and-scrum.markdown10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/kanban-vs-todo-and-scrum.markdown b/doc/kanban-vs-todo-and-scrum.markdown
index 4e083ff8..ea97811c 100644
--- a/doc/kanban-vs-todo-and-scrum.markdown
+++ b/doc/kanban-vs-todo-and-scrum.markdown
@@ -11,8 +11,8 @@ Kanban vs Todo lists
### Kanban:
-- Multiple phases, each column represent a step
-- Bring focus and avoid multitasking because you can set a work in progress limit per column
+- Multiple phases, each column represents a step
+- Bring focus and avoid multitasking by setting a work-in-progress limit per column
Kanban vs Scrum
---------------
@@ -23,15 +23,15 @@ Kanban vs Scrum
- Do not allow changes during the iteration
- Estimation is required
- Uses velocity as default metric
-- Scrum board is cleared between each sprint
+- 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 anytime
+- 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
+- Kanban doesn't impose strict constraints or meetings; process is more flexible