Kanban Condensed & KSD Course Flashcards
What is Kanban?
Kanban is a method for defining, managing, and improving services that deliver knowledge work
Which are Kanban values?
- Transparency
- Balance
- Customer Focus
- Commitment
- Flow
- Leadership
- Understanding
- Agreement
- Respect
Which are Kanban agendas?
- Sustainability
- Service Orientation
- Survivability
Which are Kanban principles?
Change Management:
- Start with what you do now
- Agree to pursue improvement through evolutionary change
- Encourage acts of leadership at every levels
Service Delivery:
- Understand and focus on customer needs and expectations
- Manage the work, let people self-organise around it
- Evolve policies to improve outcomes
Which are Kanban practices?
- Visualize
- Limit WiP
- Manage the flow
- Make policies explicit
- Feedback loops
- Improve and evolve
What is Little’s Law? What is it used for?
Little’s Law says that in a flow system that is not trending, there is a simple relationship between the averages of selected and delivered items over a selected period.
Little’s Law formula: Delivery Rate (mean) = WiP (mean) / Lead Time (mean)
Little’s Law is used to calculate the average Delivery Rate of working items in a kanban system, but it can be used to calculate the average of other metrics within the kanban system, for instance the average Throughput.
What does STATIK stand for? What is it used for?
STATIK stands for Systems Thinking Approach to Introducing Kanban.
It is a process that defines a number of steps in order to introduce Kanban in an organisation. The process considers the full system rather than isolated component parts.
Which are STATIK steps?
Step 0: Identify services
For each service:
Step 1: Understand what makes the service fit for purpose for the customer
Step 2: Understand sources of dissatisfaction with the current system
Step 3: Analyze demand (random, seasonal, chaotic, planned)
Step 4: Analyze capacity
Step 5: Model the workflow
Step 6: Discover classes of services (expedite, fixed date, standard, intangible)
Step 7: Design the kanban board (columns, swimlanes, WiP limits, other policies, commitment and delivery points, customer delivery point, structure of the work items)
Step 8: Socialize the system and board design and negotiate implementation
What is Litmus test? What is it used for?
Litmus test consists of a series of four questions and follow up questions that is used in order to assess the progress with Kanban in an organisation, and suggest areas of improvement.
Which are Litmus test questions?
- Has management behaviour changed to enable Kanban?
- Has the customer interface changed, in line with Kanban?
- Has the customer contract changed, informed by Kanban?
- Has your service delivery business model changed to exploit Kanban?
What is Litmus question and follow-up questions about management behaviour?
- Has management behaviour changed to enable Kanban?
- Is management behaviour consistent with Kanban’s deferred commitment, pull system approach?
- Are WiP limits respected by management at the system level, not just at a personal level?
- Is customer focus always an understood reason for change?
What is Litmus question and follow-up questions about customer interface?
- Has the customer interface changed, in line with Kanban?
- Is the approach to scheduling and selecting customer requests based on a pull system with limited WiP?
- Are the commitment and delivery points clearly defined and are records of Lead Times and Delivery Rates available?
- Is there a regular Replenishment Meeting?
What is Litmus question and follow-up questions about customer contract?
- Has the customer contract changed, informed by Kanban?
- Are commitments made to the customer based on the agreed or understood service levels (explicit service level agreements or service level expectations)?
- Are these levels based on probabilistic forecasting using the kanban system’s observed Lead Times and Delivery Rates?
What is Litmus question and follow-up questions about service business model?
- Has your service delivery business model changed to exploit Kanban?
- Does the service delivery business model use classes of service appropriately, based on an understanding of business risks (for example, the cost of delay) to facilitate selection decisions and inspire queuing discipline policies for work items? Are you understanding customer expectations and how they cluster into similar groups? Are you probing for posible new classes of service to improve the flow of value to the customer?
- Is there capacity in the system to hedge risks from different sources of demand and different types of work? For example, can resources be diverted to priority tasks during high-demand periods?
- Are interdependent services aggregated and coordinated to increase system liquidity and enable system levelling in light of risks and variability?
What is the commitment point? Where do you place it in the flow?
The commitment point is the point in a kanban system at which the commitment is made to delivery a work item. The customer wants the item and will take delivery of it, and the service will deliver it.
The commitment point can be when items are selected to be worked on during the Replenishment Meeting.