Master the language of WIP limits, flow metrics, and cumulative flow diagrams. Intermediate
0 / 22 completed
1 / 22
Your team's Kanban board has a WIP limit of 3 on the "In Progress" column. It currently shows three items in progress. A developer finishes a task in the "Review" column and wants to immediately pull a fourth item into "In Progress".
What is the correct Kanban response to this situation?
The Kanban principle here is: "Stop starting, start finishing." When a WIP limit is reached, the correct response is to swarm on existing work to move it forward — not to bypass the limit:
Action
Effect
Pull new item despite WIP limit
Increases multitasking; slows everything down; invalidates the WIP limit
Help finish an in-progress item
Reduces WIP; improves flow; frees up capacity for the new item faster
Raise the WIP limit
Should only happen after deliberate team discussion and retrospective evidence — not ad hoc
WIP limits exist to surface bottlenecks and encourage collaboration. A developer can review code, test a feature, or pair on a blocker — all of which move existing items forward without starting new ones.
2 / 22
Your team is introducing flow metrics to stakeholders. The engineering manager asks:
"When you say cycle time improved from 4 days to 2 days, does that mean we're responding to customer requests twice as fast?"
Which response correctly explains the difference between cycle time and lead time?
Lead time and cycle time measure different spans of the same work item's journey:
Metric
Starts when
Ends when
Measures
Lead time
Request is made (ticket created)
Work is delivered
Customer-perceived responsiveness
Cycle time
Work actually begins (moved to In Progress)
Work is delivered
Team's processing efficiency
An item may sit in the backlog for 3 weeks before being started. Lead time = 3 weeks + cycle time. Cycle time alone doesn't tell you how long the customer waited — it only measures once development is underway. To answer the manager's question: improving cycle time is good, but reducing lead time is what customers actually feel.
3 / 22
At the team's weekly metrics review, the tech lead says:
"In the past two weeks, the team closed 11 work items: 8 user stories and 3 bug fixes."
Which Kanban flow metric is the tech lead reporting?
Throughput is the number of work items a team completes per unit of time. It is Kanban's primary output metric and counts items regardless of their size or complexity:
Metric
Unit
What it tells you
Throughput
Items per week / sprint
How much work exits the system per time period
Velocity
Story points per sprint
Scrum-specific; not directly equal to item count
Cycle time
Days per item (average)
How quickly individual items flow through
Throughput is particularly useful for forecasting: based on 11 items per 2-week period, the team can project how many items they'll complete over the next quarter. Throughput does not require estimation — it is pure observation of completed work.
4 / 22
The team reviews their Cumulative Flow Diagram (CFD) in the weekly metrics meeting. They notice that the "In Progress" band has been widening steadily over the past week while the "Done" band barely grew.
What does this pattern most likely indicate?
In a CFD, a widening band in any column indicates that work is accumulating there faster than it is flowing out — a classic bottleneck signal:
CFD pattern
Meaning
Action
In Progress band widens
Incoming rate exceeds completion rate
Reduce WIP; identify and clear blockers
Review band widens
Reviews are backing up (not enough reviewers)
Pull reviewers from other tasks; limit review WIP
All bands stable, slopes parallel
Healthy, predictable flow
Maintain current practices
The widening "In Progress" band combined with a flat "Done" band is a warning sign that items are being started at a rate the team cannot sustain. The correct response is to stop starting new work and focus on completing what is already in progress.
5 / 22
Your team's Kanban board has a red horizontal lane at the top, spanning all columns above the regular rows. The team lead explains: "This is our expedite lane — only use it if absolutely necessary."
What is the correct purpose of this expedite swimlane?
An expedite lane (also called a "red lane" or "fast lane") is a special swimlane reserved for items that genuinely cannot wait for normal flow — typically production incidents, regulatory requirements, or critical customer-facing bugs:
Expedite lane characteristic
Why it matters
WIP limit of 1
Prevents the fast lane from becoming a dumping ground for anything "urgent"
Bypasses normal queue order
Ensures critical items flow to Done without waiting behind lower-priority work
Restricted entry criteria
Only items meeting a clear definition (e.g. P0 production bug) may enter the lane
The key phrase "use it only if absolutely necessary" is intentional — overuse of the expedite lane breaks normal flow and undermines the predictability the Kanban system provides. Blocked items (Option C) are typically shown with a blocker icon on their card, not moved to a separate lane.
6 / 22
During a Slack conversation about a recently submitted pull request, a senior developer comments: 'Looks like we're still seeing some bottlenecks in the API integration. The response times are consistently high, especially during peak hours.' Considering the principles of Kanban and flow optimization, what is the MOST appropriate action for the team to take based on this comment?
This question tests understanding of proactive flow optimization. Option A introduces unnecessary complexity by adding a new column without addressing the underlying problem. Option B is counterproductive; simply prioritizing doesn't solve the *cause* of the bottleneck. Option D incorrectly shifts responsibility and ignores the team's role in managing flow.
Option C correctly focuses on investigating the root cause – analyzing metrics like latency— which is a fundamental aspect of Kanban and flow management, allowing the team to identify and mitigate the 'bottleneck' described in the Slack message.
7 / 22
PR Description: 'Just finished implementing the new user authentication flow. It's working great! Now need to pull in another story – the one about reporting errors. Let's get it done!'
The Product Owner responds with: 'Hold on, team. We have three items currently in progress according to the board. Adding another directly into 'In Progress' will likely increase our WIP and negatively impact flow.' What does this response primarily highlight regarding Kanban principles?
This response correctly identifies that the Product Owner is emphasizing the core principle of Work In Progress (WIP) limits within Kanban. Maintaining WIP at or below a defined level prevents overloading the system and ensures sustainable flow. The incorrect options misinterpret the situation – prioritizing user stories isn't inherently wrong, technical details aren't relevant to the PR description, and increasing columns wouldn't solve the underlying issue of excessive WIP.
8 / 22
Your team is using Kanban to manage a feature development project. During a daily standup, a developer mentions they've finished testing a new component and are now ready to integrate it into the main branch. However, the team's WIP limit for the 'Integration' column is currently at 2. What should the developer do according to Kanban principles?
Consider the importance of managing work in progress within defined limits to maintain flow
The correct response is to discuss with the team. Kanban emphasizes collaboration and finding a solution that respects the WIP limit. Simply bypassing the limit would disrupt flow and likely lead to more bottlenecks later. Re-prioritization or adjusting scope might be necessary, but should be done collectively.
9 / 22
During a Slack conversation about a recently submitted pull request, a senior developer comments: 'Looks like we're still seeing some bottlenecks in the API integration. The response times are consistently high, especially during peak hours.' Considering the principles of Kanban and flow optimization, what is the MOST appropriate action for the team to take based on this comment?
This question tests understanding of proactive flow optimization. Option A introduces unnecessary complexity by adding a new column without addressing the underlying problem. Option B is counterproductive; simply prioritizing doesn't solve the *cause* of the bottleneck. Option D incorrectly shifts responsibility and ignores the team's role in managing flow.
Option C correctly focuses on investigating the root cause – analyzing metrics like latency— which is a fundamental aspect of Kanban and flow management, allowing the team to identify and mitigate the 'bottleneck' described in the Slack message.
10 / 22
PR Description: 'Just finished implementing the new user authentication flow. It's working great! Now need to pull in another story – the one about reporting errors. Let's get it done!'
The Product Owner responds with: 'Hold on, team. We have three items currently in progress according to the board. Adding another directly into 'In Progress' will likely increase our WIP and negatively impact flow.' What does this response primarily highlight regarding Kanban principles?
This response correctly identifies that the Product Owner is emphasizing the core principle of Work In Progress (WIP) limits within Kanban. Maintaining WIP at or below a defined level prevents overloading the system and ensures sustainable flow. The incorrect options misinterpret the situation – prioritizing user stories isn't inherently wrong, technical details aren't relevant to the PR description, and increasing columns wouldn't solve the underlying issue of excessive WIP.
11 / 22
Your team is using Kanban to manage a feature development project. During a daily standup, a developer mentions they've finished testing a new component and are now ready to integrate it into the main branch. However, the team's WIP limit for the 'Integration' column is currently at 2. What should the developer do according to Kanban principles?
Consider the importance of managing work in progress within defined limits to maintain flow
The correct response is to discuss with the team. Kanban emphasizes collaboration and finding a solution that respects the WIP limit. Simply bypassing the limit would disrupt flow and likely lead to more bottlenecks later. Re-prioritization or adjusting scope might be necessary, but should be done collectively.
12 / 22
During a Slack conversation about a recently submitted pull request, a senior developer comments: 'Looks like we're still seeing some bottlenecks in the API integration. The response times are consistently high, especially during peak hours.' Considering the principles of Kanban and flow optimization, what is the MOST appropriate action for the team to take based on this comment?
This question tests understanding of proactive flow optimization. Option A introduces unnecessary complexity by adding a new column without addressing the underlying problem. Option B is counterproductive; simply prioritizing doesn't solve the *cause* of the bottleneck. Option D incorrectly shifts responsibility and ignores the team's role in managing flow.
Option C correctly focuses on investigating the root cause – analyzing metrics like latency— which is a fundamental aspect of Kanban and flow management, allowing the team to identify and mitigate the 'bottleneck' described in the Slack message.
13 / 22
PR Description: 'Just finished implementing the new user authentication flow. It's working great! Now need to pull in another story – the one about reporting errors. Let's get it done!'
The Product Owner responds with: 'Hold on, team. We have three items currently in progress according to the board. Adding another directly into 'In Progress' will likely increase our WIP and negatively impact flow.' What does this response primarily highlight regarding Kanban principles?
This response correctly identifies that the Product Owner is emphasizing the core principle of Work In Progress (WIP) limits within Kanban. Maintaining WIP at or below a defined level prevents overloading the system and ensures sustainable flow. The incorrect options misinterpret the situation – prioritizing user stories isn't inherently wrong, technical details aren't relevant to the PR description, and increasing columns wouldn't solve the underlying issue of excessive WIP.
14 / 22
Your team is using Kanban to manage a feature development project. During a daily standup, a developer mentions they've finished testing a new component and are now ready to integrate it into the main branch. However, the team's WIP limit for the 'Integration' column is currently at 2. What should the developer do according to Kanban principles?
Consider the importance of managing work in progress within defined limits to maintain flow
The correct response is to discuss with the team. Kanban emphasizes collaboration and finding a solution that respects the WIP limit. Simply bypassing the limit would disrupt flow and likely lead to more bottlenecks later. Re-prioritization or adjusting scope might be necessary, but should be done collectively.
15 / 22
During a Slack conversation about a recently submitted pull request, a senior developer comments: 'Looks like we're still seeing some bottlenecks in the API integration. The response times are consistently high, especially during peak hours.' Considering the principles of Kanban and flow optimization, what is the MOST appropriate action for the team to take based on this comment?
This question tests understanding of proactive flow optimization. Option A introduces unnecessary complexity by adding a new column without addressing the underlying problem. Option B is counterproductive; simply prioritizing doesn't solve the *cause* of the bottleneck. Option D incorrectly shifts responsibility and ignores the team's role in managing flow.
Option C correctly focuses on investigating the root cause – analyzing metrics like latency— which is a fundamental aspect of Kanban and flow management, allowing the team to identify and mitigate the 'bottleneck' described in the Slack message.
16 / 22
PR Description: 'Just finished implementing the new user authentication flow. It's working great! Now need to pull in another story – the one about reporting errors. Let's get it done!'
The Product Owner responds with: 'Hold on, team. We have three items currently in progress according to the board. Adding another directly into 'In Progress' will likely increase our WIP and negatively impact flow.' What does this response primarily highlight regarding Kanban principles?
This response correctly identifies that the Product Owner is emphasizing the core principle of Work In Progress (WIP) limits within Kanban. Maintaining WIP at or below a defined level prevents overloading the system and ensures sustainable flow. The incorrect options misinterpret the situation – prioritizing user stories isn't inherently wrong, technical details aren't relevant to the PR description, and increasing columns wouldn't solve the underlying issue of excessive WIP.
17 / 22
Your team is using Kanban to manage a feature development project. During a daily standup, a developer mentions they've finished testing a new component and are now ready to integrate it into the main branch. However, the team's WIP limit for the 'Integration' column is currently at 2. What should the developer do according to Kanban principles?
Consider the importance of managing work in progress within defined limits to maintain flow
The correct response is to discuss with the team. Kanban emphasizes collaboration and finding a solution that respects the WIP limit. Simply bypassing the limit would disrupt flow and likely lead to more bottlenecks later. Re-prioritization or adjusting scope might be necessary, but should be done collectively.
18 / 22
During code review, a developer writes: 'The API response time for this endpoint is consistently exceeding 500ms. We need to investigate potential bottlenecks in the data processing logic.' What does this comment primarily highlight regarding flow within the Agile process?
This comment focuses on a key metric – response time – which directly impacts flow. Exceeding 500ms likely indicates a blockage or inefficiency within the process that's hindering progress toward sprint objectives. The other options represent tangential concerns or potential solutions rather than addressing the immediate issue of slow API performance.
19 / 22
A team member sends a Slack message: '@john_doe Just finished implementing the new user onboarding flow. It's passing all tests, but I'm seeing some intermittent failures when scaling up to 50 concurrent users. Need to investigate!' What does this message suggest about the current state of the Kanban workflow?
The message highlights 'intermittent failures' when scaling. This strongly indicates a flow constraint – the onboarding process isn't robust enough to handle increased demand. The core Kanban principle of optimizing flow is being challenged here. Simply stating it's 'passing all tests' doesn't reflect its practical performance under load.
20 / 22
You are drafting a Pull Request description: 'Implemented the user profile update functionality. Resolved several UI bugs and improved data validation. Now ready for review.' Which of the following best describes the primary focus of this PR description within an Agile/Kanban context?
While functional code is important, the description's emphasis on 'UI bugs' and 'data validation' without connecting it to user experience or overall team goals reveals a narrow focus. Agile emphasizes delivering value incrementally – this description misses that crucial link to the bigger picture of flow optimization.
21 / 22
During a daily stand-up, a developer states: 'I finished implementing the payment processing integration. I've deployed it to staging and am waiting for QA.' What does this statement primarily contribute to within a Kanban-driven workflow?
The key takeaway here is that the developer *completed* a task. This directly impacts WIP – reducing the number of incomplete items in the system. Acknowledging completion allows the team to reassess and optimize flow accordingly; the other options focus on secondary or problematic aspects.
22 / 22
A developer receives an API response: 'Error Code: 429 – Too Many Requests. Rate limit exceeded.' Considering the Agile/Kanban context, what does this indicate about potential flow issues?
A '429 Too Many Requests' error signals a bottleneck – the API is overwhelmed. This directly impacts flow by limiting the number of requests the system can handle efficiently. Addressing this requires optimizing the integration to improve throughput and prevent further rate limit violations.
What will I practice in "Kanban & Flow Vocabulary | Agile & Scrum Exercises"?
This is an Agile & Scrum exercise set. It walks through 22 scenario-based multiple-choice questions built around real usage of Agile & Scrum terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 22 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the Agile & Scrum vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Agile & Scrum exercises?
See the Agile & Scrum exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — Agile & Scrum vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.