Questions for the PSK-I were updated on : Dec 01 ,2025
True or False: When the Developers add Kanban to Scrum, the way they use the Sprint Goal
during their Daily Scrum changes.
A
Explanation:
When Developers add Kanban to Scrum, the way they use the Sprint Goal during their Daily Scrum
can change. In traditional Scrum, the Sprint Goal is a shared commitment for the Sprint. However, in
Professional Scrum with Kanban, the focus shifts to the flow of work and delivering value
incrementally.
While the Sprint Goal still provides direction, the Daily Scrum may involve discussions about:
Progress towards the Sprint Goal: How are we progressing towards the overall goal?
Work in Progress (WIP): Are we adhering to WIP limits?
Blockers and impediments: What is preventing the team from progressing?
Prioritization: Are we working on the highest-value items?
By focusing on these aspects, the team can ensure that they are delivering value continuously and
efficiently.
True or False: Little's Law is used to forecast a Scrum Team's output.
B
Explanation:
Little's Law is a formula used to understand the relationship between system throughput, work-in-
progress (WIP), and lead time. While it can be used to analyze and optimize the flow of work, it is not
specifically designed for forecasting a Scrum Team's output.
Scrum Teams typically use techniques like story point estimation and historical velocity to forecast
their output.
What is the best chart to determine when a single item that has not been started will be
finished?
(choose the best answer)
A
Explanation:
A Cycle Time scatterplot is the best chart to determine when a single item that has not been started
will be finished. This chart shows the distribution of cycle times for completed work items. By
analyzing the historical data, you can estimate the likely cycle time for a new item.
Here's how to use the Cycle Time scatterplot:
Identify the average cycle time: Calculate the average cycle time for similar types of work items.
Consider variability: Look at the range of cycle times to understand the variability in delivery times.
Estimate completion time: Based on the average cycle time and variability, estimate when the new
item is likely to be completed.
While the other charts (CFD, Throughput run chart, and WIP Aging chart) provide valuable insights
into the overall workflow, they are not as effective for predicting the completion time of a single
item.
As input for Daily Scrum, which metrics are likely to provide the most actionable data?
(choose the best answer)
A
Explanation:
Leading indicators are the most appropriate metrics for Daily Scrum because they provide
information about the current state of the work and potential future issues. By tracking leading
indicators, the team can identify potential problems early on and take proactive measures to address
them.
Here are some examples of leading indicators that can be useful during Daily Scrum:
WIP Limits: Are the WIP limits being adhered to?
Blocked Tasks: Are there any tasks that are blocked or waiting for dependencies?
Task Progress: How much progress has been made on each task?
Team Mood: Is the team morale high or low?
By discussing these leading indicators during the Daily Scrum, the team can identify any
impediments and take immediate action to keep the work flowing smoothly.
Lagging indicators, on the other hand, provide information about past performance and are not as
useful for identifying and addressing current issues. Examples of lagging indicators include cycle
time, lead time, and throughput. While these metrics are important for long-term analysis and
improvement, they are not as actionable in the context of the Daily Scrum.
Which of the following is NOT a flow metric?
(choose the best answer)
B
Explanation:
While WIP is a crucial metric for Kanban teams, it is not a flow metric. Flow metrics measure the
movement of work through the system, while WIP measures the amount of work currently in
progress.
Here's a breakdown of the other options:
Cycle Time: The time it takes to complete a piece of work from start to finish.
Throughput: The rate at which work is completed.
Work item age: The amount of time a work item has spent in the system.
All of these metrics provide insights into the flow of work and can be used to identify bottlenecks
and optimize the workflow.
Therefore, option B, "Work in Progress (WIP)," is the correct answer.
For teams practicing Professional Scrum with Kanban, what are the most appropriate metrics
to inspect?
(choose the best answer)
A
Explanation:
For teams practicing Professional Scrum with Kanban, the most appropriate metrics to inspect are:
Control Chart: This chart helps visualize process stability and identify any significant deviations from
the expected behavior. By tracking key metrics like lead time and cycle time, teams can identify
trends and potential issues.
Cumulative Flow Diagram (CFD): The CFD provides a visual representation of the flow of work
through the system. It helps teams understand bottlenecks, identify areas for improvement, and
assess the overall health of their workflow.
Aging Chart: This chart shows the age of work items as they progress through the workflow. It helps
teams identify items that are taking too long to complete and prioritize them accordingly.
These metrics are particularly relevant for Kanban teams because they focus on the flow of work and
the identification of bottlenecks. By tracking these metrics, teams can make data-driven decisions to
optimize their workflow and improve delivery performance.
Options B, C, and D are not the most appropriate metrics for Kanban teams. Story points and
historical velocity are more commonly used in Scrum, while t-shirt size is a relative estimation
technique that may not be suitable for all Kanban teams.
When is the most appropriate time for Scrum Teams practicing professional Scrum with
Kanban to inspect and adapt their Work in Progress (WIP) Limits?
(choose the best answer)
D
Explanation:
In the context of Professional Scrum with Kanban, the Sprint Retrospective is the most suitable time
to inspect and adapt WIP Limits. This is because the Retrospective is a dedicated time-box for the
Scrum Team to reflect on its performance and identify areas for improvement.
Here's why:
Continuous Improvement: The Retrospective is a key part of the Scrum framework, designed to
foster continuous improvement. By reviewing WIP Limits during this time, the team can assess their
effectiveness and make data-driven decisions.
Data-Driven Decisions: By tracking WIP Limits over time, the team can gather valuable insights into
their workflow and identify bottlenecks. This data can inform decisions about adjusting WIP Limits to
optimize flow and productivity.
Team Collaboration: The Retrospective provides an opportunity for the entire team to discuss and
agree upon changes to WIP Limits. This collaborative approach ensures buy-in and commitment from
all team members.
While it's true that Developers can monitor WIP Limits throughout the Sprint, the Retrospective is
the designated time for a formal review and adjustment. This ensures that any changes are aligned
with the team's overall goals and strategy.
When using Kanban in a Scrum environment, some resistance toward introducing Work in Progress
(WIP) Limits may be encountered. What is an alternative to introducing WIP Limits in Kanban?
A
Explanation:
Although WIP limits are central to Kanban, enhancing visualization and communication through
Kanban boards can be a way to ease into WIP limits gradually. This alternative fosters transparency
and alignment without directly imposing WIP constraints, which can be beneficial for teams adjusting
to Kanban practices. Reference: The Kanban Guide for Scrum Teams.
Which statements best describe the purpose of a Scrum Team’s Definition of Workflow?
(Choose the best three answers)
ACF
Explanation:
The Definition of Workflow clarifies how value moves through the system, establishes a shared
understanding of when work items are considered to be in progress and completed, and enhances
transparency, particularly around WIP limits. This provides structure to the Kanban system within
Scrum and helps the team optimize their flow and maintain consistency. Reference: The Kanban
Guide for Scrum Teams.
What is the best use for the Work Item Aging metric?
(Choose the best two answers)
BC
Explanation:
Work Item Aging is an essential metric that helps the Scrum Team monitor progress and detect
potential delays early. It is especially useful in Daily Scrums to identify items that are taking longer
than expected, allowing the team to take corrective actions and prevent delays. It also serves as a
leading indicator of how long the feedback loop for a Work Item may take.
True or False: A Scrum Team using Kanban does not need to craft a Sprint Goal during Sprint
Planning. They can instead create one “on-demand” as new work flows into the Sprint Backlog.
B
Explanation:
Even when using Kanban, Scrum Teams still follow the Scrum framework, which mandates crafting a
Sprint Goal during Sprint Planning. The Sprint Goal provides focus and alignment for the team,
ensuring that all work contributes toward a common objective, rather than being taken on as
needed. Reference: The Scrum Guide.
Scrum Teams using Kanban can start to increase predictability by:
C
Explanation:
By limiting WIP, Scrum Teams using Kanban create a more predictable flow, as it prevents the team
from overcommitting and encourages them to finish work items before starting new ones. This aligns
with Kanban’s principle of optimizing flow and Scrum’s iterative delivery approach. Reference: The
Kanban Guide for Scrum Teams.
In the context of Scrum, which of the following statements about Cycle Time are true?
(Choose the best two answers)
BC
Explanation:
Cycle Time measures the time taken to complete individual work items, and while some items might
take longer than a Sprint, on average, teams aim to have Cycle Times shorter than the Sprint
duration to ensure a smooth flow and regular delivery of value. Reference: The Kanban Guide for
Scrum Teams.
When using Kanban, it is useful to have explicit policies. What existing elements in the Scrum Guide
might be used as explicit policies?
D
Explanation:
Kanban emphasizes explicit policies for better transparency and alignment, and elements such as the
Definition of Done, Definition of Ready, and Product Backlog refinement can be utilized as explicit
policies to clarify the Scrum Team’s working agreements. These policies help the team make
consistent decisions and streamline their processes. Reference: The Kanban Guide for Scrum Teams
and The Scrum Guide.
What does it mean when a Scrum Team chooses to communicate an 85% 5-day service level
expectation (SLE)?
C
Explanation:
An SLE of 85% for 5 days signifies that the team anticipates they will complete items within 5 days,
85% of the time. This helps set clear expectations with stakeholders, ensuring transparency around
potential delivery timelines. The SLE is based on historical data and provides a probability-based
forecast, rather than a commitment. Reference: The Kanban Guide for Scrum Teams.