summaryrefslogtreecommitdiff
path: root/doc/kanban-vs-todo-and-scrum.markdown
diff options
context:
space:
mode:
authorFrederic Guillot <fred@kanboard.net>2017-01-29 11:07:42 -0500
committerFrederic Guillot <fred@kanboard.net>2017-01-29 11:07:42 -0500
commit0371acff89b14b9bdcb03e72fd9637e26e6b517c (patch)
treef5878c9c07705379d137843cb8f92e3cdf7c20a8 /doc/kanban-vs-todo-and-scrum.markdown
parent3bf4789be255650b64f42231f41383cb13b65572 (diff)
Move English documentation to folder en_US
Diffstat (limited to 'doc/kanban-vs-todo-and-scrum.markdown')
-rw-r--r--doc/kanban-vs-todo-and-scrum.markdown37
1 files changed, 0 insertions, 37 deletions
diff --git a/doc/kanban-vs-todo-and-scrum.markdown b/doc/kanban-vs-todo-and-scrum.markdown
deleted file mode 100644
index ea97811c..00000000
--- a/doc/kanban-vs-todo-and-scrum.markdown
+++ /dev/null
@@ -1,37 +0,0 @@
-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