Managing project risks with Kanban13 Sep 2022

How a company approaches risk management can often be what makes or breaks it. While Kanban does not prescribe many rules in general, its support for a steady flow style of work allows risk management to be incorporated into it without problems.

Performance charts spread across a table in an office

Performance history

The most forthright advantage that using Kanban for your process management brings, in terms of dealing with risks, is that it gathers your past performance data. It's invaluable for the process of identification of the root causes of repeatable problems. It can also help you estimate what percentage of a specific work is likely to expect a delay and what size. Such insight will aid your delivery time estimations for clients.

The added WIP limitations

Applying Kanban's WIP limits to processed work allows for risks to be minimized by avoidance: there is less that can go wrong at any time since you're limiting how many work items are started all at once.

Differentiating tasks by risk level

With each work item having a type assigned, not only do you gain the ability to limit how many things are worked on simultaneously, you can also decide how many out of each type can be worked on at once. It furthermore reduces the danger of investing time into risk-posing jobs. Additionally, we can devise a class of service for each of the task types. Keeping a specific protocol of action for the various types of work (so, for work items with varied levels of built-in risk) minimizes the risks further still.

For example, in software development, there usually is a set action protocol for a bug critical to the software's existance and performance - it will have the highest urgency. The provided fix will need to be tripple-checked for potential impact on all other software elements, and its deployment will have the highest prority. Meanwhile, the procedure for working on a new, non-crucial feature will be much more relaxed: do the best you can to achieve the goal, test how well it works and integrates with the other elements, and we'll deploy it when the time is right. It's also common for tasks on the opposite spectrum of importance to be assigned to developers with different experience and skill levels.

Risk sizing

The strength of using card colors for low, high and critical risk types is its simplicity and high readability. But if what you're after is a more precise risk estimation, you can go ahead and give it numerical values.

Kanban Tool board with tasks showing individual risk values

Typically, the values assigned to the risk size on specific actions come down to weighing the impact of the risk coming to life with the likelihood of it happening (risk = impact * likelihood). You can use the outcome of the above multiplication as your total risk value, or you can keep the two factors separate and assign tasks to workers based on their competence and infallibility appropriate to the read risk points.

Summing up, there would be several ways to visualize and tackle risks on your Kanban board:

  • card types/colors
    (e.g., red tasks -> existential risk, orange tasks -> high risk, yellow -> minor bug reported by clients, with all other types of work given various shades of gray type colors);
  • risk values
    a number based on your risk calculation, board columns sorted either by that number - from highest down, or by the order in which assigned tasks need to be done in;
  • an "Expedited" swimlane
    a presence of a task in the expedited row means that all other work must stop until the high-risk tasks are done. It's possibly the most simple, visual, and effective solution;
  • or, a combination of any of the above.
Woman sitting with a team at an office table

A final, uncomplicated way to minimize risks - strongly connected to kanban daily practices - is briefly discussing the more risky work items (e.g., the orange and red ones) before tackling them technically. By relying on the collective power of all team members, you're more likely to foresee potential hiccups and issues than if you leave the matter in the hands of one specialist.

Trouble focusing when working from home? Let us help!30 Aug 2022

For many of us, being able to focus was always a challenge - bigger or smaller. Now, we're asked to do it while working from home, either full-time or partly. Depending on what it was that's been making concentrating on the task at hand difficult for you, moving work to your home can either...

13 Kanban Board Examples for 202204 Aug 2022

#toc_container {display:table; font-size:100%; margin-bottom:1em;} #toc_container li, #toc_container ul, #toc_container ul li {list-style:outside none none !important;} Whether you're managing a team, are a part of one, or lead the life of a freelancer, or all of the above, we suspect...

Is introducing Agile Marketing easy? No, but you should do it anyway.23 Jun 2022

An Agile take on marketing has the same objectives as Agile software development: meeting the customers' needs quicker and better. The speed in action is a must in a world where your competition can shake up the market with a single Instagram story or Youtube video, receiving client responses...

Why should you identify the value chain in your business?09 Jun 2022

An attractive, competitive offer for customers is the core part of running a business. The value that your product or service provides is what makes or breaks the company in the long term. So, to remain in business, you should focus on finding ways to make your services as valuable to the...

How to run a virtual team status meeting well?24 May 2022

Is your immediate answer to the title's question something like: "it's nothing hard, just jump on a video conference call and get the participants to say what they're doing!" ? If so, we'd guess you either don't run such meetings too often or have an extra powerful hold over your team members,...

Agile management adoption roadblocks & solutions04 May 2022

What is Agile management? At the core of an Agile way to manage an organization is the ability to change goals, innovate and adopt new working strategies in a speedy yet lightweight manner, while maintaining respect for workers and sticking with the company's big picture goals. In other...

How to introduce Kanban to your team?19 Apr 2022

By now - over a decade since the Kanban method's introduction to knowledge work - most people have at least heard about it, if not tried it. If you're considering adopting Kanban for your team, here are a few tips on making it a success. Kanban is a way of organizing work by splitting all...

A comprehensive list of benefits of using online project management16 Feb 2022

Having worked on the kanbantool.com service for over a decade, it's rather difficult for our team to imagine people not using some form of a workflow management system. But a recent trip to fellow business offices made us think about such individuals, as well as teams. It seems that an easy way...

How to manage Agile epics in Kanban Tool?11 Jan 2022

What's an epic? In Agile workflow management, the term epic can hold different meanings for various people and teams. Some see an epic as a general outline or sketch of a task. For others, it's a goal that breaks down into a series of small jobs. There will also be those people for whom each...