Skip to main content


LEAN Principles

LEAN principles originated in Japan with the “Toyota Production System” and have evolved from manufacturing. Tools and techniques for LEAN are rocking the world of Information Technology (LEAN IT). LEAN does not stand alone! There is a DevOps Foundation certification class available that explains how LEAN, AGILE and ITSM dove tail together to optimize a DevOps integrated delivery pipeline. The core idea is to deliver customer value while eliminating waste (Muda). The goal is to provide value to the customer through a perfect value creation process that has zero waste.

What About KANBAN?

KANBAN is one of many techniques utilized for LEAN practices and results in an increase in productivity and value for individuals and teams. In Japanese the word KAN means visual and the word BAN means board. KANBAN is a visual board that helps teams to visualize work and get more done. If you’re reading this because you are interested in using KANBAN for yourself or your team, here is an inexpensive online e-learning, self-paced course available titled “Spotlight on KANBAN”. It is a great resource.

KANBAN starts with a list of tasks on the left. There are color-coded cards (sticky notes) for each task that physically get moved through work in progress fields until the card/task finally ends in the DONE column on the right. KANBAN is like an expanded to-do list. These tasks can be completed by one individual, many individuals or teams. Visualizing the work and seeing tasks moved to DONE gives the team a sense of accomplishment and inspires them to keep moving forward.

The KANBAN board is a pull system. This means that it is the voice of the customer or the customer requirement that determines/pulls the work. This keeps the teams focused on creating VALUE for customers. Also, teams prioritize and pull work when they are ready for it to prevent overburden. KANBAN ensures that the work being performed is customer focused. Because the focus is on moving tasks to DONE, the KANBAN helps to reduce Work in Progress (WIP). We can have a whole lot of effort and teams can appear to be working very hard but if there are a hundred things in progress and nothing moved to DONE, where is the VALUE? Reducing idle time and WIP is a key benefit of using a KANBAN tool.

Although traditional KANBAN boards are on walls or whiteboards, there are many electronic KANBAN tools that work well for remote teams. Start with your own template, create it with tape on a whiteboard or look for an e-KANBAN. Start today to realize the power so that you too KAN KANBAN! 

For more information click here KANBAN


Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

The ITIL® Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem