The main objectives of the Toyota Production system, which is one of the primary sources of inspiration for Kanban for knowledge work, were to get rid of overburden (muri) and inconsistency (mura), and eliminate waste (muda) from your system.
Last couple of month updates of SwiftKanban focused on some of the key features like Cycle Time Threshold, revamped ESP Analytics and Enhanced To-Do Board and there are several enhancements done with this update.
Personal productivity and time management tools/methods have always been a subject of interest. Numerous methods and tools have been developed over the years. However, few seem to stick over time. Given that any tool or method needs a certain level of discipline at an individual level, is there a method that can really help you manage better, visualize what you need to do and most importantly, stick? In this blog, I am going to share my own experience of tackling this challenge.
Last September, as a new member of the Digité Marketing team, I was trying hard to understand Digité products and space which we are in. I was learning several new concepts including Lean, Agile, Application Lifecycle Management (ALM), Project Program Management, etc. where we have a bunch of powerful tools!
Cycle time (or System Lead Time as some call it) is one of the most common metrics used to measure the effectiveness of a Kanban system. Cycle time is the time taken by a Kanban card to move from start to end on the board (or some part thereof). As you start using a Kanban system and implementing its principles, ideally the cycle time of the system should reduce.
It is not enough to Visualize. You need to be prepared to See!A genuine fear lurks while putting final changes to this article a few weeks before the 45th President of the United States takes office. Becoming the most powerful man on the planet is a fine example of a huge and successful project and his phenomenal success flies in the face of some key takeaways in this article. So, reader’s discretion is advised!
With the December update, we have made a huge breakthrough in 2 major areas which have been in our backlog for a long time and have been repeatedly requested by customers across the globe. “Visualization” is the primary goal of Kanban and the Kanban board is the heart of any Kanban system. Any team working with Kanban follows one key principle - to have all the work items visualized on the board. But over a period of time, as more and more item-types get added, it can become difficult for team members to keep track of important work items and their status as they are spread across the board. In large team Kanban systems, this can be a significant issue.
One of the important aspects of The Kanban Method is Class of Service (CoS). CoS is a risk categorization mechanism for any work item. We identify 4 Classes of Service – Standard, Fixed Date, Expedite, and Intangibles – depending on customer expectation, value and loss of business value identified as cost of delay. For this blog, cards that are classified as Intangible CoS will be referred to as “Intangibles”.
Enterprise/ Portfolio Kanban has for some time provided a visual method of defining and managing portfolios in a much easier manner compared to traditional PPM tools. Kanban Boards can be set up at different levels of the organization to track a portfolio of initiatives, programs, or product releases and their underlying projects or work items can be visualized and tracked far more easily than ever possible traditionally.