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 the

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with