From 0371acff89b14b9bdcb03e72fd9637e26e6b517c Mon Sep 17 00:00:00 2001 From: Frederic Guillot Date: Sun, 29 Jan 2017 11:07:42 -0500 Subject: Move English documentation to folder en_US --- doc/kanban-vs-todo-and-scrum.markdown | 37 ----------------------------------- 1 file changed, 37 deletions(-) delete mode 100644 doc/kanban-vs-todo-and-scrum.markdown (limited to 'doc/kanban-vs-todo-and-scrum.markdown') 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 -- cgit v1.2.3