Please login or join to subscribe to this thread
Kanban Boards are part of Visual Project Management. If taken seriously, it provides a great basis for the team (and also other stakeholders) to see the project progress and it supports communication.
My approach to project/program/portfolio management is this: I use tools and techniques that best fits for the initiative where I am working on. To understand what tool and technique (and above of that what method) to use I always make an impact analysis taking into account the actual state of the organization. That is critical because for systemic thinking applied to organizations you have to understand that each thing you introduce into your organization will impact the organization as a whole then you have to take into account the whole organizational architecture. With all that said, then first of all you have to understand what Kanban is and after that the tools and techniques it proposed to see if applies to your initiative. I´d like to know about the history and evolution too because it helps me to find other ways to use the methods, tools and techniques.
Within our team, we had discussed using a Kanban Board to help visualize our project queue - assisting with a simpler overview of where each sits, modify prioritization, and resource allocation.
But thinking at the organization level, Sergio brings up an important point. Tools cannot just be implemented with a proper process. Change is very difficult for employees, so it is important to do the work up front to help ensure the move is right for the organization.
Two benefits of proper use of Kanban boards are:
1. They provide quick, visual understanding of work progress which can reduce effort for communicating status updates and increase transparency.
2. Setting work in process limits ensures that wasteful inventory is not built up and that continuous flow is maintained. These limits need to be monitored and adjusted based on the productivity and capacity assigned to each stage of the workflow.
Kanban boards can be used with any type of project lifecycle - while they are popular on projects following an agile delivery approach, nothing prevents their usage on more predictive projects.
Kanban boards are part of Low Tech High Tools. They are visual, easy to comprehend, Shows progress and limits can be used for easy identification of bottlenecks and improved productivity.
Kanban board (whiteboard or paper) close to the team. The team then updates it with "Post-it". Very visual and easy for intrested Managers to see progression. When project reports arrives to them, they already know part of the Project Progression.
Please login or join to reply