Agile Kanban Method and Practices Questions and Answers 1 — Questions and Answers
Question 1: A team has adopted the Kanban method and is using a board to visualize their workflow. They notice that work items are piling up in the 'Testing' column, and developers are frequently idle. Which core Kanban practice should the team implement to address this issue directly?
- Implement feedback loops
- Make process policies explicit
- Limit Work in Progress (WIP) (Correct answer)
- Encourage acts of leadership at all levels
Correct answer: Limit Work in Progress (WIP)
Limiting Work in Progress (WIP) is a fundamental practice in Kanban designed to prevent bottlenecks and improve flow. By setting a limit on the number of items allowed in the 'Testing' column, the team would be forced to address the testing bottleneck before pulling new work into the system, thereby creating a smoother, more predictable workflow.
Question 2: A key principle of the Kanban Method is to 'Start with what you do now.' What does this principle imply for a team beginning their Kanban adoption?
- The team must immediately discard their existing processes and adopt a predefined Kanban workflow.
- The team should overlay Kanban practices on their current workflow, respecting existing roles and responsibilities. (Correct answer)
- The team is required to define all roles, such as Service Delivery Manager, before starting.
- The team must first complete a comprehensive process re-engineering project before visualizing their workflow.
Correct answer: The team should overlay Kanban practices on their current workflow, respecting existing roles and responsibilities.
The 'Start with what you do now' principle emphasizes that Kanban is an evolutionary, non-disruptive method for change. It advocates for applying Kanban principles and practices to the current process, respecting the value of existing roles, responsibilities, and processes, and then making incremental changes over time.
Question 3: In a Kanban system, which of the following is the primary purpose of making process policies explicit?
- To assign blame when work items are delayed.
- To create a common understanding of how work flows through the system. (Correct answer)
- To eliminate the need for team meetings and discussions.
- To enforce a strict, unchangeable set of rules for the workflow.
Correct answer: To create a common understanding of how work flows through the system.
Making process policies explicit, such as defining what 'Done' means for each stage or when an item can be pulled into the next column, creates a shared and transparent understanding for everyone on the team. This clarity helps to reduce ambiguity and ensures consistency in how work is performed, which is essential for managing flow and enabling collaborative improvement.
Question 4: A marketing team is using a Kanban board to manage their content creation process. They want to improve their ability to deliver articles to customers faster. Which Kanban metric would provide the most direct insight into the total time elapsed from a customer's request to its fulfillment?
- Work in Progress (WIP)
- Throughput
- Cycle Time
- Lead Time (Correct answer)
Correct answer: Lead Time
Lead Time is the total time a work item spends in the system, from the moment it is requested (committed to) until it is delivered to the customer. This is distinct from Cycle Time, which measures the time from when work actively begins on an item. To understand the full customer experience, Lead Time is the most appropriate metric.
Question 5: A software development team using Kanban holds a brief, daily meeting in front of their board to coordinate their activities for the day. This meeting is an example of which core Kanban practice?
- Limiting WIP
- Managing Flow
- Implementing Feedback Loops (Correct answer)
- Making Policies Explicit
Correct answer: Implementing Feedback Loops
The daily stand-up meeting, often called the 'Kanban Meeting', is a key type of feedback loop. It provides a frequent, short cycle of inspection and adaptation, allowing the team to review the state of the workflow, identify blockers, and synchronize their efforts to keep work flowing smoothly.
Question 6: Unlike Scrum, which uses time-boxed Sprints, the Kanban method is characterized by what kind of delivery approach?
- A phase-gated, sequential model
- A continuous flow model (Correct answer)
- A project-based, big-bang delivery
- A release-driven, quarterly cycle
Correct answer: A continuous flow model
The Kanban method is fundamentally a continuous flow system. Work items are pulled into the workflow as capacity becomes available, rather than being planned in fixed-length iterations like Scrum Sprints. This allows for a more flexible and continuous delivery of value.
Agile Kanban Method and Practices Questions and Answers 1
A team has adopted the Kanban method and is using a board to visualize their workflow.
They notice that work items are piling up in the 'Testing' column, and developers are frequently idle.
Which core Kanban practice should the team implement to address this issue directly?