Project Management Tool – Kanban Board
- 1. Project Management Tool – Kanban Board S.Sudha Velan B.E (Civil)
- 3. • Kanban (Japanese: 看板, meaning signboard or billboard) • Kanban is a visual system used to manage and keep track of work as it moves through a process. The word kanban is Japanese and roughly translated means “card you can see.”
- 4. Kanban board • A kanban board is an agile project management tool designed to help visualize work, limit work-in-progress, and maximize efficiency (or flow).
- 5. Kanban Visual System • Kanban is a visual system for managing work as it moves through a process. The goal of Kanban is to identify potential bottlenecks in your process and fix them so work can flow through it cost-effectively at an optimal speed or throughput. •
- 6. The following are the six most common types of Kanban cards : 1. Withdrawal or Conveyance Kanban Cards. ... 2. Supplier Kanban Cards. ... 3. Emergency Kanban Cards. ... 4. Express Kanban Cards. ... 5. Production Kanban Cards. ... 6. Through Kanban Cards
- 8. The Six General Practices of Kanban • 1. Visualize the process. • This is where Kanban cards come into play. Once you can actually see work, the number of requests, the amount of time it takes to deliver on a request, who is making the requests, and risks, you can take steps to manage them better individually and as a team. Cards are placed on a Kanban board so all team members can follow the current workflow. • 2. Control work in progress (WIP). • This is a cornerstone of Kanban. One should limit the WIP. Thus, it forces the team to focus on a limited number of tasks and work to completion. Also, it spotlights where work is being obstructed in the delivery pipeline before a situation becomes critical. • 3. Manage flow • Based on the data gathered on cycle time and other agreed upon metrics, and using information about the current state of work on the board, Kanban helps visually track and manage tasks to deliver maximum value
- 9. • 4. Communicate policies explicitly • Kanban teams work together to create basic rules about workflows for different items, when to move an item into the next lane or row, and how to note and manage blocked work tasks. These items are near the board, and the team works toward improvement. • 5. Implement feedback • Most Kanban teams do daily standup meetings in front of their Kanban board. They discuss ways to improve task delivery and overall process. Also, they check for elimination of waste . • 6. Collaborate for improvement, evolve experimentally. • A Kanban system shines a light on the areas that call for improvement. Once highlighted, workgroups develop a way to solve the problem, hypothesize, and test solutions.
- 12. Advantages • Versatility • Kanban is versatile, and as such spans industries and job roles, meaning that it can be used right across your company. • Continuous improvement • The visual aspect of Kanban means that progress is simple to monitor and review. This means that changes can be made easily if waste is identified. • Responsiveness • The “just-in-time” delivery origin means that inventory can be matched with demand, enabling more agile responses to business needs. • Higher output • As WIP is limited, the team is encouraged to work collaboratively to complete tasks, increasing focus and reducing the risk of distractions, such as multi- tasking. • Team empowerment • Ownership and responsibility of the process is shared amongst the whole team, allowing innovative and efficient decisions. • Product perfection • The focus on continuous improvement and quality control throughout the process reduces the number of errors and means less rework. The product will therefore be more accurate.
- 13. Disadvantages • Kanban board misuse • You must ensure that the tasks on the Kanban board are kept up-to-date to ensure that the process continues to flow smoothly with no backlog of tasks. • The Kanban board can be as complicated as you make it, so keep it simple and avoid overcomplication. • Unspecific timelines • The continuous shift of tasks on the Kanban board mean that predicting timelines of completion becomes difficult. This is due to the pull production system. • Unsuitable for dynamic projects • Kanban assumes that the project is somewhat stable and consistent, meaning that it is ineffective in industries where projects aren’t static. • Potential bottlenecks • If one card becomes blocked, due to a lack of action on another card then the process may become stuck. The emphasis on cards in this process makes scheduling difficult and presents a greater risk than other methodologies
- 17. Thanks & Regards S.Sudha Velan