Scrum PSK-I - Professional Scrum with Kanban (PSK 1) Exam

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​.

A Cycle Time Scatterplot is a visualization tool used to display the cycle times for individual work items over time. This scatterplot provides several types of qualitative information:

1.General Cycle Time Trends (Option A): The scatterplot can show general trends over time, such as whether the cycle times are decreasing, increasing, or staying stable. This helps teams understand the overall direction in which their workflow efficiency is moving.

2.Single Cycle Time Outliers (Option B): The scatterplot also helps identify individual outliers — work items that took significantly longer or shorter than usual to complete. These outliers can be further investigated to understand why they occurred and to prevent similar situations in the future.

3.Clusters of Cycle Time Outliers (Option C): In addition to single outliers, the scatterplot may reveal clusters of outliers. These clusters can indicate systemic issues, such as bottlenecks or recurring problems in a specific part of the process.

Since a Cycle Time Scatterplot provides all these types of information (general trends, single outliers, and clusters of outliers), the correct answer is D.

When WIP limits are implemented, Developers are encouraged to focus on completing existing tasks rather than starting new ones. This leads to a more collaborative approach, as team members may swarm to complete items together. Additionally, limiting WIP enhances transparency in the process, which in turn strengthens self-management by the team. These principles align with Kanban’s emphasis on active management and the Scrum framework's focus on collaboration. References: The Kanban Guide for Scrum Teams​​.

The primary effect of limiting Work in Progress (WIP) is to create a pull system. A pull system ensures that new work is only started when there is capacity, meaning that work is "pulled" into the system when the team has the availability to do so. This approach prevents overloading the team and helps maintain a steady and predictable flow of work, aligning with the Kanban practices within the Scrum framework

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 cycletime, 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.

If the Product Owner requests that an urgent, unplanned work item be added during the Sprint, and it aligns with the Sprint Goal but does not fit within the current WIP limits, the Developers should:

1.Add the urgent item to their Sprint Backlog but only start working on it when their WIP Limits allow it (Option A): This maintains the integrity of the WIP limits and ensures that the team doesn't overcommit or create too much work in progress, which could affect flow and focus.

2.Take on the urgent item as an exception to the WIP Limits and visualize that they are above their WIP Limit (Option C): By taking on the urgent item as an exception, the team can address the urgency while being transparent about the temporary breach of the WIP limits. This visualization helps the team and stakeholders understand the current state of work and its impact(

Options B (Adjust the WIP Limits) and D (Reject the urgent item) are less suitable because they either undermine the WIP control mechanism or fail to accommodate a potentially critical change that aligns with the Sprint Goal.

Little's Law states:

•Average Cycle Time = Average Work in Progress (WIP) / Average Throughput.

Little's Law is used to understand and forecast the performance of a workflow system. It implies that if you know two of these three variables (Cycle Time, WIP, Throughput), you can calculate the third. The correct formula is Option A(

Options B, C, and D do not correctly state Little's Law.

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.

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