Kanban Flashcards
Kanban Practices
- Visualize the workflow
- Limit work in progress (WIP)
- Manage flow
- Define each stage explicitly
- Implement feedback loops
- Improve collaboratively, evolve experimentally
Kanban
-A method for providing material/product to a succeeding operation by signaling the preceding operation when more material/product is needed. This “pull” type of process control employs a Kanban, a card or signboard, attached to a lot of material/product in a production line signifying the delivery of a given quantity. When all of the material/product has been processed, the card/sign is returned to its source, where it becomes an order to replenish.
- Popular method for managing tasks in Lean and Agile environments
- A way of thinking about tasks and progress that enhances use of the board
- just-in-time scheduling tool, not a management tool
What is a Kanban Board?
- Contains tasks and columns. Typically these include:
1. Backlog or To-Do
2. A column for each stage: for example, in a software development environment these might be Code, Document, Test, and Build
3. Done
Generally, you’ll find that columns on a Kanban board are laid out in the same orientation as the script you use for writing. Right to left
-You should be able to move a task through the stages required without ever moving it backwards on the Kanban board. Progress needs to be forward, not backward. Some experimenting might be needed to come up with alayout that suits your team’s working style.
Why Use a Kanban Board?
- Offers a quick, visual impression of how a sprint or project is progressing, that’s why the don’t send a task backwards rule is so strict, it messes up that visual impression of progress
- Helps team grasp the full process that every task needs to go through
How to Use a Kanban Board
- At the state of a sprint or project, write every task on a card or post-it note.
- Add these tasks to the Backlog or To-Do column.
- Each person in the team picks a task, adds their name to it, and moves it to the next column.
- Rules vary depending on methodology, typically one person should have one take only assigned to them at a time. That’s the task they are working on at the moment.
- If they are not working on it, it should be unassigned so anyone who’s free can take it over
Kanban Principles
- Start with your existing workflow
- map out and use that to create your Kanban board
- Make small, incremental changes
- make small changes regularly and letting everyone get used to the modified process
- Respect your current way of doing things
- Kanban encourages us to assume that those things exist for a reason and to change as required, slowly
- Encourage leadership in everyone
- Everyone takes responsibility for identifying issues and coming up with solutions to improve processes