diff options
| -rw-r--r-- | README.markdown | 2 | ||||
| -rw-r--r-- | docs/kanban-vs-todo-and-scrum.markdown | 37 | ||||
| -rw-r--r-- | docs/what-is-kanban.markdown | 32 |
3 files changed, 71 insertions, 0 deletions
diff --git a/README.markdown b/README.markdown index bf47b605..06e4bae5 100644 --- a/README.markdown +++ b/README.markdown @@ -50,6 +50,8 @@ Documentation #### Introduction +- [What is Kanban?](docs/what-is-kanban.markdown) +- [Kanban vs Todo Lists and Scrum](docs/kanban-vs-todo-and-scrum.markdown) - [Usage examples](docs/usage-examples.markdown) #### Working with projects diff --git a/docs/kanban-vs-todo-and-scrum.markdown b/docs/kanban-vs-todo-and-scrum.markdown new file mode 100644 index 00000000..3d53023a --- /dev/null +++ b/docs/kanban-vs-todo-and-scrum.markdown @@ -0,0 +1,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 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 predefined roles like scrum master, product owner and the team +- A lot of meetings: planning, backlog 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 diff --git a/docs/what-is-kanban.markdown b/docs/what-is-kanban.markdown new file mode 100644 index 00000000..e3c3cf53 --- /dev/null +++ b/docs/what-is-kanban.markdown @@ -0,0 +1,32 @@ +What is Kanban? +=============== + +Kanban is a methodology originally developed by Toyota to be more efficient. + +There is only two constraints imposed by Kanban: + +- Visualize your workflow +- Limit your work in progress + +Visualize your workflow +----------------------- + +- Your work is visualized on a board, you have a clear overview of your project +- Each column represent a step in your workflow + +Bring focus and avoid multitasking +---------------------------------- + +- Each phase can have a work in progress limit +- Limits are great to identify bottlenecks +- Limits avoid working on too many tasks in the same time + +Measure performance and improvement +----------------------------------- + +Kanban uses lead and cycle times to measure performance: + +- **Lead time**: Time between the task is created and completed +- **Cycle time**: Time between the task is started and completed + +By example, you may have a lead time of 100 days and only have to work 1 hour to complete the task. |