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.markdown54
1 files changed, 26 insertions, 28 deletions
diff --git a/doc/kanban-vs-todo-and-scrum.markdown b/doc/kanban-vs-todo-and-scrum.markdown
index 4e083ff8..184a3f6b 100644
--- a/doc/kanban-vs-todo-and-scrum.markdown
+++ b/doc/kanban-vs-todo-and-scrum.markdown
@@ -1,37 +1,35 @@
Kanban vs Todo lists and Scrum
-==============================
Kanban vs Todo lists
---------------------
-### Todo lists:
+Todo lists [ lista de tareas ]:
-- Single phase (just a list of items)
-- Multitasking possible (not efficient)
+Fase unica (es solo una lista de tareas)
+Multitarea posible (no eficiente)
-### Kanban:
+Kanban:
+
+Multi fases,
+Concentración absoluta para evitar multitareas por que se puede establecer un limite por columna para mejorar el progreso
-- Multiple phases, each column represent a step
-- Bring focus and avoid multitasking because you can set 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 each sprint
-- 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
-- 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
+
+Scrum:
+
+Los sprints son time-boxed, usualmente 2 o 4 semanas
+No permitir cambios durante la iteración
+La estimación es requerida
+Utiliza la velocidad como métrica predeterminada
+El tablero de Scrum se borra entre cada sprint
+Scrum tiene funciones predefinidas como scrum master , los dueños del producto y el equipo
+Una gran cantidad de reuniones: planeaciones, backlogs grooming, daily stand-up, retrospectiva
+
+Kanban:
+
+Fluido continuo
+Los cambios se pueden crear en cualquier momento
+La estimacion es opcional
+Usa la iniciativa del tiempo de ciclo para apresurar el performance
+el tablero Kanban board es persistente
+Kanban no impone estrictas restricciones y reuniones, el proceso es mas flexible