PSK-I Exam Dumps - Scrum Professional Scrum with Kanban Questions and Answers

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. References: The Kanban Guide for Scrum Teams​​.

Lagging indicator metrics are metrics that provide information about past performance:

1.Velocity (Option A): This is a measure of the amount of work a Scrum Team completes in a Sprint. It is a lagging indicator because it reflects what has been done rather than predicting future performance.

2.Cycle Time (Option B): This metric measures the time taken to complete a work item from start to finish. It is a lagging indicator because it provides data on how long work items took to complete in the past.

3.Throughput (Option D): This refers to the number of work items completed in a given period. Like Velocity, it reflects past performance and is considered a lagging indicator.

Work in Progress (Option C) and Work Item Aging (Option E) are not lagging indicators:

•Work in Progress (C): is a current state metric that indicates how much work is currently in progress.

•Work Item Aging (E): is a leading indicator, providing insights into how long a work item has been in progress, helping predict delays or bottlenecks

Sprints remain a core aspect of the Scrum framework, regardless of the use of Kanban. Sprints provide a time-boxed cadence and structure that is integral to Scrum. The addition of Kanban practices enhances Scrum but does not replace the need for Sprints. References: The Kanban Guide for Scrum Teams​.

An SLE combines a timeframe (elapsed days) and a probability, representing the likelihood that a work item will be completed within that timeframe. This helps to set realistic expectations for stakeholders and guide the team in maintaining a predictable flow. References: The Kanban Guide for Scrum Teams​.

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. References: The Kanban Guide for Scrum Teams and The Scrum Guide​​.

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.

This statement is incorrect. A Scrum Team will not stop using Sprints just by implementing Kanban. Kanban is used to complement Scrum practices, not replace them. The team continues to use Sprints as a cadence and timebox for delivering increments of work while also incorporating Kanban principles like visualizing work, limiting WIP, and managing flow to enhance their process

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.

Cycle Time measures the time it takes for a single work item to go from start to completion. By understanding Cycle Time, a team can forecast when multiple items from the Product Backlog will likely be finished based on the average duration it takes to complete an item. This is essential in Kanban as it provides insight into the delivery timeline and is crucial for planning and predictability within a Scrum context. References: The Kanban Guide for Scrum Teams​.

Within the same Kanban system, Work in Progress (WIP) is not a leading indicator for "Story points delivered." While WIP can influence throughput and cycle time, it does not directly correlate with story points delivered, as story points are a measure of effort or complexity rather than flow. The number of story points delivered is not directly influenced by the current WIP levels