Reading the Signs: Kanban CFD Patterns
To improve workflows, first, you should understand how to identify problem areas. The Kanban method uses visual methods for evaluating your processes. The Kanban cumulative flow diagram is a particularly powerful tool. The CFD records the number of tasks in each process state at regular intervals, generally daily or weekly.
As work progresses and the amount of data grows, the CFD plots a visual history of the project. At a glance, you can track lead times, work in progress, and spot problems brewing. Today we’ll show you how to recognize the most common Kanban CFD patterns and explain what they mean for your project.
1. Differences in gradient
Meaning: Mismatched arrivals and departures. This is probably the most common Kanban CFD pattern you will come across. Usually, the upper line of a band will be steeper than the lower one. Tasks are entering the stream faster than they are being completed, work in progress is increasing, cycle times become slower.
Solution: Strictly enforce WIP limits and consider reducing them – stop new tasks entering the process state until outstanding tasks are delivered. In the more unusual case when the lower band line is steeper than the upper band line (work delivery rate is faster than arrival rate), get your team members to focus on speeding up upstream process states.
2. Flat lines
Meaning: Flat lines in your cumulative flow diagram represent periods of zero departures – zero tasks being completed or zero tasks moving to the next downstream process state. This Kanban CFD pattern indicates something is blocking your process and no value is being delivered to the customer!
Solution: Identify and resolve the blockage. Ask your team what is holding up the workflow – they could be waiting on a review or verification. Brainstorm ways of solving the issue and getting things moving again.
3. Stair steps
Meaning: Tasks are being delivered (or moved to the next downstream process state) in batches. A band line will stay flat and then show a sudden “stair step”. This doesn’t necessarily signify a problem, but batch deliveries can make your system less predictable than continuous delivery.
Solution: Are batch deliveries necessary for the project? Consider implementing a continuous delivery system and see how your predictability and cycle time are improved. Alternatively, try increasing the frequency of batch deliveries.
4. Bulging bands
Meaning: One or more bands increase in thickness, either gradually or suddenly. The bulging band Kanban CFD pattern indicates WIP is increasing in this process state. Large WIP results in longer cycle times.
Solution: What is causing our WIP to increase? First, eliminate benign explanations – if your team size has increased recently, your WIP limit has probably increased to make use of the extra capacity. Next, look for other causes. Are tasks being pushed by the management instead of pulled by the team? Is there a blockage in a downstream process state? Try separating tasks in a process state into Ongoing and Done – adding Done states or queue states lets you spot bottlenecks where work is idle with no one working on it.
5. Disappearing bands
Meaning: A process state stops being picked up on your cumulative flow diagram. There are few different possible meanings behind this Kanban CFD pattern – tasks could be skipping a process state in the workflow, tasks could be moving to the next process state faster than the CFD recording interval, or an upstream blockage is stopping tasks getting to this state.
Solution: The first step with this CFD pattern is to identify the cause. The simplest step to start with is decreasing the CFD recording interval to see if the band reappears. Next, check for process states being skipped – it could mean that this state is unnecessary to your Kanban workflow. Finally, introduce queue states (Done states) in order to identify hidden blockages. Splitting process states into Ongoing and Done will let you see where work is collecting idly and not being pulled through.
6. The S-curve
Meaning: This S-curve Kanban CFD pattern emerges between two flat spots on the cumulative flow diagram – points with zero WIP. It is characterized by a flat beginning section, followed by a steep middle section, and finishing again with a flat end section. Zero WIP not only signals that there are inefficiencies in your workflow, but it also makes your process far less predictable. With an S-curve CFD pattern, the gradient of your CFD is variable and forecasting becomes less accurate.
Solution: WIP should be as consistent as possible – find and solve the issues causing zero WIP flat spots. Is there a lack of team members available to pull work through? Is there a blockage in an upstream process state? Removing the flat spots will bring the S-curve back to a consistent gradient.
As you can see, the cumulative flow diagram is a simple but powerful tool to analyze your process. Learning to identify the most common Kanban CFD patterns will allow you to evaluate your process and spot problem areas at a glance.
What is the most common CFD pattern you observe in your process? What type of issues do you experience? How do you resolve these issues? Tell us about your experience in the comments!
Meet the Author
Sonya Siderova is a passionate product manager and a driving force behind Nave, a Kanban analytics suite that helps teams become more efficient through data-driven decision making. When she's not catering to her two little ones, you might find Sonya absorbed in a good heavyweight boxing match or behind a screen crafting a new blog post.
Learn how to integrate the Principles of Influence with the Fit-For-Purpose framework and the Kanban Method through… https://t.co/97I5jdsIG1Follow
Two Kanban roles, Service Request Manager and Service Delivery Manager have emerged to equip teams with important d… https://t.co/QrpmJ0i45SFollow
Are you struggling to perform accurate delivery predictions? Download our complete guide to forecasting!… https://t.co/KSThETGbKMFollow
Product teams who use Nave to analyze their workflow can make empirical predictions based on their performance data… https://t.co/FPYPwRmuhLFollow
Are you ready to recap the benefits Kanban analytics can bring to your workflows? Choose your platform, and get sta… https://t.co/Id41c55WmZFollow
With the Nave Kanban Analytics Power-Up for Trello, you'll see beyond your Kanban boards. Analyze your workflow, id… https://t.co/7OqdMb1R5RFollow
Learn more about the Kanban System Accelerator and how is it used within Duke Energy’s Agile Capability Center.… https://t.co/mjtRIiKo8gFollow
Businesses that are truly fit for purpose are positioned for long-term survival and success. Here's an in-depth rev… https://t.co/0tMEyPT8R0Follow
Try our advanced Kanban analytics suite for free on your favorite tool and start leveraging the power of data-drive… https://t.co/nFM71d32nLFollow
Product teams often argue which is better, but the focus should be on how to merge Kanban and Scrum together to del… https://t.co/rd9rS1VZPlFollow
Learn more about the experience of changing an organization with 130 years of history and more than 2,000 employees… https://t.co/T6YfSoJBL2Follow
Did you ever wonder what’s cooking behind the doors of Nave laboratory? Now you can take a peek inside our product… https://t.co/cAHqkCD8enFollow
The key to battle process bottlenecks is to fully recognize but not fight the symptoms. Instead, managers need to a… https://t.co/SLO3QON7B1Follow
Are you ready to recap the benefits Kanban analytics can bring to your team? Start your free 14-day trial today!… https://t.co/hfT9ty5esnFollow
Having a self-funded SaaS company keeps your mind sharp and reminds you how important your initiative is from both… https://t.co/BXKt2ZIFVpFollow
Jira teams can now use Nave to optimize their software development processes. Follow our three-step guide to get st… https://t.co/DtxfR4IykCFollow
It’s all about trust, respect and appreciation. If your employees are engaged, have a purpose and feel motivated, t… https://t.co/sBYwDottlRFollow