Covers visualizing workflow and limiting work in progress, core flow metrics and Little's Law, service level expectations, and integrating Kanban practices with Scrum values and the Scrum framework.
20 free sample questions252 in the full practice test
A Scrum Team has just adopted Kanban practices. During the Daily Scrum, a Developer mentions they are blocked on an item that has been in the 'Testing' column for four days. The team's Service Level Expectation (SLE) is 5 days with 85% confidence. What is the most appropriate action for the Scrum Master to facilitate?
Answer and explanation
Correct answer: C
The primary purpose of tracking Work Item Age is to serve as a leading indicator of potential problems. When an item is aging and blocked, it signals a risk to the SLE. The Daily Scrum is the perfect event to inspect progress toward the Sprint Goal and adapt the plan. The most effective action is to make the problem visible and facilitate a team-based solution to unblock the item and restore its flow, rather than waiting for the SLE to be breached.
Q2Question 2
BeginnerMultiple answers
Complementary Practices · Kanban Practices
According to the Kanban Guide for Scrum Teams, which of the following should the visualization of a Scrum Team's Definition of Workflow include? (Select THREE)
Answer and explanation
Correct answers: A, B, E
Explicit policies say how work moves through each state, such as what must be true before an item is pulled. They can include parts of the Definition of Done.
Clear start and finish points tell the team when an item becomes work in progress and when it is finished. Cycle Time runs from the start point to the finish point. Work Item Age counts from the start point.
The team defines what a work item is, most likely a Product Backlog item. Then everyone counts and tracks the same units of value on the board.
Q3Question 3
Beginner
Understanding and Applying the Scrum Framework · Understanding and Applying the Scrum Framework
True or False: A Scrum Team using Kanban practices must replace its Sprint Burndown chart with a Cumulative Flow Diagram (CFD).
Answer and explanation
Correct answer: B
False. Scrum with Kanban does not require any particular chart. Burn-downs, burn-ups and cumulative flow diagrams are optional ways to track progress. The team may keep its burn-down, switch to a CFD, or use both.
Q4Question 4
Advanced
Complementary Practices · Agile Metrics for Kanban
A marketing team at a retail company uses Scrum with Kanban to manage campaigns. During a Sprint Retrospective, they analyze their Cycle Time Scatterplot and notice a wide distribution of cycle times, ranging from 2 to 20 days. The Product Owner is concerned because this makes forecasting unreliable. What is the most likely root cause the team should investigate first?
Answer and explanation
Correct answer: B
Blocked or waiting items keep aging while other items flow. That spreads Cycle Times far apart and makes forecasts unreliable. Responding quickly to blocked items helps narrow the spread.
Q5Question 5
Advanced
Complementary Practices · Kanban Practices
Case Study: HealthData Inc.
HealthData Inc. is a company that processes patient data for clinical trials. Their core Scrum team is responsible for a workflow that includes Data Ingestion, Anonymization, Validation, and Reporting. Sprints are two weeks long. The team consistently fails to deliver the forecasted work, causing delays in trial reporting and frustrating stakeholders. The team's board has columns for each workflow step but no WIP limits. During Daily Scrums, Developers often report being 'busy' but it's unclear what is close to being 'Done'.
The Validation step is a known bottleneck. It requires a manual review by a senior data scientist, of which there is only one. Work frequently piles up in a 'Ready for Validation' column. To address their unpredictability, the management has mandated the team adopt Kanban practices.
Which of the following actions represents the most effective first step for the Scrum Team to take in their next Sprint Planning?
Answer and explanation
Correct answer: C
The most effective first step is to address the known bottleneck and the overall system load. Setting a WIP limit on 'Validation' (e.g., 2-3 items) makes the bottleneck's capacity explicit and prevents work from piling up. A second, broader WIP limit on the entire system (from start to near the end) encourages a pull system and prevents the team from starting too much work overall. This evolutionary approach respects the current process, makes the key problem visible, and starts the journey toward better flow without drastic, disruptive changes like eliminating Scrum.
Q6Question 6
Advanced
Complementary Practices · Agile Metrics for Kanban
When applying Little's Law (Average Cycle Time = Average WIP / Average Throughput), which of the following conditions must be true for the calculation to be reasonably accurate?
Answer and explanation
Correct answer: A
Little's Law is a queuing theory formula that holds true for any stable system. For the law to provide meaningful insights in a Kanban context, the system's key characteristics (like average arrival rate and average departure rate) should be stable. This means the workflow isn't undergoing constant, radical change, and the averages for WIP and Throughput are calculated over a sufficiently long period to be representative of the system's typical performance.
Q7Question 7
Intermediate
Complementary Practices · Kanban Practices
A Scrum Team's workflow includes a 'Peer Review' step before an item can be moved to 'Done'. The team decides to implement a WIP limit. Which of the following is an expected outcome of applying a WIP limit to the 'In Progress' and 'Peer Review' columns?
Answer and explanation
Correct answer: D
By limiting WIP in the 'In Progress' columns, Developers will eventually reach a point where they cannot pull new work without an existing item moving forward. If items are waiting in 'Peer Review', the system signals that the most valuable action is to perform a review to free up WIP capacity. This creates a pull system, improving flow and fostering collaboration by encouraging team members to help where the work is needed most.
Q8Question 8
Intermediate
Complementary Practices · Agile Metrics for Kanban
During Sprint Planning, a Product Owner wants to know how many items from the Product Backlog the team can likely complete in the upcoming Sprint. The team has been using Kanban for several Sprints. Which flow metric provides the most useful historical data for this type of forecasting?
Answer and explanation
Correct answer: C
Throughput measures the number of work items finished per unit of time (e.g., per Sprint). By analyzing historical Throughput data (e.g., the team has completed between 8 and 12 items in each of the last 5 Sprints), the team can create a probabilistic forecast for the upcoming Sprint. While Cycle Time is used to forecast single items, Throughput is used to forecast how many items can be completed in a fixed time period.
Q9Question 9
Beginner
Understanding and Applying the Scrum Framework · Understanding and Applying the Scrum Framework
The Scrum value of 'Focus' is directly supported by which Kanban practice?
Answer and explanation
Correct answer: B
Limiting Work in Progress (WIP) directly supports the Scrum value of Focus. By setting WIP limits, the team agrees to concentrate on a small number of items at a time. This reduces context switching, prevents individuals from being overloaded, and encourages the entire team to focus on finishing work before starting new work. This collective focus helps in delivering a valuable Increment each Sprint.
Q10Question 10
Intermediate
Complementary Practices · Kanban Practices
A team is designing its first Kanban board. They have identified the following steps for their work: 'To Do', 'Analysis', 'Development', 'Testing', 'Deployment'. To properly measure Cycle Time for their development process, where should the 'Start Point' and 'Finish Point' of their workflow be defined?
Answer and explanation
Correct answer: C
The start and finish points for measuring Cycle Time should align with the process the team wants to improve and forecast. Typically, this starts when the team commits to working on an item (pulling it from the backlog into an active state like 'Analysis' or 'Development') and ends when the item delivers value or is ready for delivery (e.g., after 'Testing'). The 'To Do' state is often a queue of options, not committed work, and 'Deployment' might be a separate process. The key is that the team explicitly defines these points.
Register free for 10 more questions
Or unlock all 252 PSK-I questions with explanations, timed mode and flashcards.