When multiple teams, various tools, and stakeholders from across the business are involved, IT Service Management (ITSM) processes can be complicated and challenging to manage — but Kanban can help. We’ve created new board templates, based on ITIL guidelines, to quickly get started on managing and implementing your ITSM processes. These new Kanban board templates will give your team the visibility it needs to take a systems-thinking approach to prioritizing and managing problems, changes, and incidents — resulting in faster time to resolution and reduced costs.
Keep reading to learn how your team can use these Kanban board templates, with specific examples of some of your most common workflows: incident resolution, problem and incident management, change authorization, and change implementation.
Recently, a group of my LeanKit coworkers and I were talking Kanban. The age-old debate surrounding the definitions of lead time and cycle time came up, and we all rolled our eyes a bit. The Lean community has rehashed this topic a million times already, but it seems we still can’t seem to reach a consensus. The topic can be confusing to those new to Kanban, and unfailingly frustrates experienced practitioners. In this post, I’ll explain why these definitions are commonly debated. I’ll also explain how a simple definition can help you make the most of these Lean metrics.
In my last post, I talked about the basic metrics of flow (cycle time, throughput, and WIP) and shared what data you’d need to collect to get started. Now that you have the data — how do you turn it into meaningful flow metrics? You’ll just need to learn a few simple Kanban calculations. In this post, I’ll share how to calculate cycle time using start and finish times of work items.
As an Accredited Kanban Trainer (AKT) and coach, I work with teams every day who are evolving their understanding of Kanban as well as the level of maturity at which their teams practice it. One of the most frequent questions I hear from the teams with whom I work is:
Do daily standups really need to happen every day?
It’s important to take into account the first principle of Kanban, Start with what you do now, when considering such a question. I decided that this would be an excellent topic for my second webinar with LeanKit. In case you missed it, you can watch the recording below. Keep reading to learn more about how teams find themselves conducting unproductive standups, day after day — and how to determine if your team is ready to graduate to less frequent standups.
My name is Chris Lee, and I am an IT Operations Engineer at LeanKit. I spend my time here automating deployments of infrastructure and researching new cloud-based technology.
In IT Operations, things change — a lot. What was your priority last week is now on the backburner because of this new, shiny priority that needs to be done yesterday. This typically creates an environment of “continuous confusion”, in which we are constantly shifting our priorities to meet the most urgent needs of the business.
Is your team under constant pressure to meet delivery dates and increase efficiency? Watch this webinar to find out how Kanban can help you get a handle on your volume of work by unhiding it and improving your flow.
Hello, my name is Geoff Craig and I am an Automation Engineer here at LeanKit. In my previous life, I worked in IT Operations for numerous companies, large and small, on projects of varying complexity.
In every IT Operations group that I’ve worked with, there were always competing priorities from different parts of the business. We kept hearing the same questions about why work wasn’t getting done. We knew the answers, but we never had a way to communicate the problems in a way people would understand — so they never got solved.
One of the reasons I came to LeanKit is that I firmly believe that visualizing the work of IT Operations can change the way we work — and thus, how the value of IT Operations is perceived in the organization.