{"id":23092,"date":"2022-01-26T19:54:25","date_gmt":"2022-01-26T18:54:25","guid":{"rendered":"https:\/\/scrum-master.org\/kanban-6-basic-practices\/"},"modified":"2024-02-11T01:19:31","modified_gmt":"2024-02-11T00:19:31","slug":"kanban-6-basic-practices","status":"publish","type":"post","link":"https:\/\/scrum-master.org\/en\/kanban-6-basic-practices\/","title":{"rendered":"Kanban: 6 basic practices"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Kanban is a workflow management method. This method allows development teams to better manage their workflow.<\/span> The Kanban<\/span> board visualizes both the process (workflow) and the actual work of the developers going through it.<\/span><\/p>\n

The aim of Kanban is to identify potential bottlenecks in your process and resolve them. So that work can proceed smoothly and at optimum speed.<\/span><\/p>\n

In<\/span>this article,we’ll look at<\/span> the 6 <\/b><\/span>\n basic practices to be implemented in the Kanban method:<\/b>\n<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

1. View Workflow<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This is the first fundamental practice for adopting and implementing the Kanban method. You must<\/span>ez <\/span>\n view<\/b>\n<\/span>,<\/span> <\/span>either on a physical board, or on a virtual <\/span>virtual Kanban<\/a>the <\/span>\n process steps<\/b>\n<\/span> you use to deliver your work or services. <\/span> <\/p>\n

Depending on the complexity of your development process, your Kanban board can be very simple (with 3 columns) or very elaborate (more than 10 columns!). Once you’ve divided your workflow into stages, you’ll be able to better visualize the work in progress.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t
Simple Kanban board with three workflow steps<\/figcaption>\n\t\t\t\t\t\t\t\t\t\t<\/figure>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

A task to be carried out by the Dev Team can take the form of Post-Its or cards<\/b> in different colors. To signify either different classes of service, or simply different types of work item (a technical task, a User Story, an Epic etc.). <\/p>\n

If you think it might be useful, your Kanban board can also have different Swimlanes <\/b>. A swimlane will allow you to filter your Post-its on a single line by theme, Usecases, or type of Backlog element (see image below). If you’re new to Kanban, I’d advise you, for the time being, to use a single horizontal Swimlane containing all your cards.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t
Kanban board with 3 columns and 3 swimlanes<\/figcaption>\n\t\t\t\t\t\t\t\t\t\t<\/figure>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

2. Limit WIP or number of tasks in progress<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Work in progress (WIP) limitation is determined by the team’s work capacity for each stage of the process. Limiting WIP <\/b><\/span>(<\/span>Work in Progress<\/span>)<\/span> effectively means setting a maximum number of Backlog\/Card\/Post-its items that a column of your workflow can accept<\/span>.<\/p>\n

Limiting work-in-progress is fundamental to the implementation of Kanban. By limiting the WIP, you encourage your team to complete current tasks, before starting a new one. This creates capacity in the system, so that new jobs can be taken on by the development team, once the previous task has been completed. This is known as “pull” flow.<\/p>\n

In the early days of implementing Kanban in your team, it can be difficult to decide what your WIP limits per column should be. So, from Many teams start with a WIP limit of 1 to 1.5 times the number of people working on a specific stage of your workflow. For example, for the “Development in progress” column, the WIP limit can be equal to 2 or 3 if you have 2 developers. This value will later be modified by a more appropriate WIP limit that you will have measured and discussed with the development team.<\/span><\/p>\n

Finally, displaying and announcing the WIP limits on each of the table’s columns not only helps team members to finish what they’re doing before starting new tasks, but also helps to communicate to the customer and the stakeholders <\/a>that there is a limited capacity to do work for this team. As a result, stakeholders and the Product Owner<\/a> (in an Agile team) will be forced to better plan the work they push on the development team.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t
Example of a Kanban board with defined WIP Limits<\/figcaption>\n\t\t\t\t\t\t\t\t\t\t<\/figure>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

3. Flow management<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The work of the<\/span> your workflow needs to be tracked and measured. Flow monitoring allows for early detection of difficulties and <\/span>bottlenecks<\/b>. That’s why you need to observe your workflow and collect as much data as possible, to improve the flow of cards on your Kanban Board.<\/span><\/p>\n

So a key aspect of this observation process is the resolution and elimination of bottlenecks. This is to examine the columns in your table and see how long the cards remain in each stage of the development process. If cards remain on a column for a long time, this is never a good sign. <\/span><\/p>\n

Reducing the time spent in each column is essential to reduce cycle time. <\/span>\n cycle time<\/b>\n<\/span>. As you improve the flow, the delivery of your team’s work becomes smoother and more predictable. As a result, it becomes easier for the team to make reliable commitments to stakeholders.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

4. Make process standards\/rules clear and explicit<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

When visualizing your process on a Kanban board, you need to explicitly define and visualize your workflow rules for how you do the work. By formulating explicit workflow rules, you create a common basis for all participants to understand how to perform any type of work in the system. <\/span><\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\"flx\t\t\t\t\t\t\t\t\t\t\t
Example of flow rules in a Kanban board with explicit columns<\/figcaption>\n\t\t\t\t\t\t\t\t\t\t<\/figure>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In an Agile team, we often use the Definition Of Done (DoD<\/a> ) and the Definition Of Ready (DoR)<\/a> to spell out the rules for each column of your Kanban board. This activity can be facilitated by the team’s Scrum Master<\/a>.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
<\/div>\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

5. Set up feedback loops<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Feedback loops are an integral part of any good system. The Kanban method encourages and helps you to implement feedback loops.<\/p>\n

The aim of feedback is to collect positive and negative opinions on the product or functionality developed. This frequent feedback can be fed back into the workflow to improve the product developed. <\/p>\n

There’s nothing worse than spending a lot of time, money and resources without collecting feedback from users. This creates a very high risk of creating a product that doesn’t correspond to the initial demand.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

6. Collaborative improvement, empirical evolution<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The Kanban method is a continuous improvement process. It allows you to make small changes to improve your team’s work rhythm. This method encourages the use of empiricism. You formulate a hypothesis, test it and make modifications based on the results of your test. As a team implementing Lean\/Agile principles, your main task is to constantly evaluate your process and continuously improve wherever possible and appropriate.<\/p>\n

The impact of each change you make can be observed and measured using the various signals your Kanban board provides. Using these signals, you can assess whether or not a change will help you improve. Then decide whether to keep it or try something else. Kanban boards help you collect much of your system’s performance data – either manually, if you’re using a physical board – or automatically, if you’re using a tool like Jira. Using this data and the metrics it helps you generate, you can easily assess whether your performance is improving or falling, and modify your system if you feel this is necessary.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Further information<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/p>\n

<\/p>\n

<\/p>\n

<\/p>\n

<\/p>\n

<\/p>\n

<\/p>\n

As usual, you’ll find our useful links below:<\/p>\n

<\/p>\n

<\/p>\n

    \n
  1. “A brief introduction to Kanban” by Atlasian: link here<\/a>.<\/li>\n
  2. “Feedback loop: How to exploit user feedback in an Agile project” by Agathe Penverne: link here<\/a>.<\/li>\n
  3. The book: The Lean Toolbox – 2nd ed. To learn more about the fundamentals of Lean (and get 64 turnkey tools in this book!) : \n link here<\/strong>\n<\/a>.<\/li>\n<\/ol>\n

    <\/p>\n

    Don’t hesitate to ask your questions in the comments!<\/p>\n

    <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

    Kanban is a workflow management method. This method allows development teams to better manage their workflow. The Kanban board visualizes both the process (workflow) and the actual work of the developers going through it. The aim of Kanban is to identify potential bottlenecks in your process and resolve them. So that work can proceed smoothly […]<\/p>\n","protected":false},"author":4,"featured_media":22570,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[149],"tags":[],"class_list":["post-23092","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-lean-kanban"],"_links":{"self":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/posts\/23092","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/comments?post=23092"}],"version-history":[{"count":0,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/posts\/23092\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/media\/22570"}],"wp:attachment":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/media?parent=23092"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/categories?post=23092"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/tags?post=23092"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}