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

# Implement feedback loops

From the strategic level down to the delivery level, there are different meetings that must happen to keep the company aligned, functioning in a rhythm, and connected.


<br>

We need to ensure the presence of mechanisms through which all levels across the organization are connected and flowing both strategically and operationally.
To achieve this, Lean organizations rely on a set of meeting cadences that happen regularly depending on the business cycles, product cycles, or delivery cycles.

Feedback loops force people to be deliberate in paying attention to the effects of their actions and decisions, which are not always evident and easy to grasp.



## Team cadences

Now, we will see which meetings a Kanban team must regularly hold.

### Daily kanban

All employees should be part of one daily meeting with their teams to discuss tactical issues, update their peers, and synchronize all employees, regardless of their level.
This is the usual daily huddle to plan for the next day and talk about dependencies and blockers.

Remember, the focus in Kanban is to optimize flow, so the first thing we do in a team’s daily huddle is to read the dashboard from right to left, focusing on blockers, and making sure that all the team is aligned into making work items flow through the system as fast as possible.

### Replenishment

This is the Kanban cadence for deciding what to select from the pool of options, commit to next work item, and replenish the input buffer for the Kanban system.

It can occur on demand or within a specific frequency, and you must agree with stakeholders and customers how often it will take place, who must attend. You must also design the agenda and decide on expected inputs and outputs of the meeting.

The following are typical activities for a replenishment meeting agenda:
* Check what is new since the last meeting.
* Inspect new arrivals to the pool of options/ideas and the “Ready to Pull” buffer.
* Ensure that work items are correctly classified for risk and classes of service are appropriate.
* Check how many Kanban slots are available and of type/class they are.
* Filter the available pool of options by type, class, and due date to gain an initial
list of candidates for selection.
* Stakeholders must select a short list of candidates.

Learn the importance of implementing feedback loops and conducting Kanban team meetings. 

Feedback Loops

Learn the importance of implementing feedback loops and conducting Kanban team meetings.

Introduction

Improving Flow

Kanban Fundamentals

Kanban to Improve Scrum

Kanban System Design

The Final Note

Feedback Loops

Implement feedback loops

Team cadences