Gain insights into Kanban fundamentals, delve into designing Kanban systems, and learn how Kanban can improve Scrum practices to boost developer productivity effectively.

This course will introduce you to Kanban fundamentals. You will begin by studying the origins of Kanban as a method for designing and improving knowledge work. 

Later in the course, you will be taught the core practices of Kanban to successfully design a Kanban System at the team level. Then, you will learn how to use Kanban to improve your Scrum practice. At the end of the course, you will be introduced to the process of designing a Kanban system.

Kanban Fundamentals: Boosting Developer Productivity



The purpose of this step is to agree on how to handle work so that all team members handle work in a consistent way. As a result, the team will
generate a list of policies governing the way work is handled.
There are four main areas that we will explore: 

* **Demand Management**
* **Side Orders (AKA Dark Matter)**
* **When to Pull**
* **Additional Policies**

# Demand management
Discuss with the team who is managing the Ready to Pull buffer or the upstream process in case of an end-to-end product team.
We also need to agree on how often the Ready to Pull buffer is replenished and prioritized. Additionally, we must go to the other end of the service and do the same for the completed work coming out of the system.

# Side orders (AKA Dark matter)
The team must agree on how to handle demands coming “from the side” (i.e., not via an official channel: chat, telephone calls, “corridor” orders, etc.). It must also agree on what to do with that work some team members are unofficially doing.

# When to pull
Ask the team when and how the work is pulled from the “Ready to Pull” buffer.
A good policy would state that a team member should pull new work only when he/she cannot contribute to any other ongoing work. If you are using WIP limits, the policy should state that work is pulled only if the WIP limit is not violated.
An excellent policy would also say that instead of violating the WIP limit and pulling new work, a team member should consider working on intangible work (e.g., improving test environment, compilation scripts, documentation, refactoring, etc.), helping another team member, or supporting the Product Owner in developing upstream options.

# Additional policies
 
Apart from these policies related to Kanban, as a team, you probably have some working agreements. If you don’t have them, you should have them as a complement to the Kanban Way-of-Working policies.




Have a look at the way work is managed through policies. 

Define Way-of-Working Policies

Have a look at the way work is managed through policies.

Introduction

Improving Flow

Kanban Fundamentals

Kanban to Improve Scrum

Kanban System Design

The Final Note

Define Way-of-Working Policies