Scrum Professional Scrum with Kanban PSK-I Exam Practice Test

Answer : A

The best answer is option A, which outlines the core Kanban practices for Scrum:

* Visualizing Flow: Helps the team see the state of work items at a glance.

* Limiting Work in Progress (WIP): Prevents overloading the team and promotes focus on completing work.

* Actively Managing the WIP: Ensures the team continuously monitors and manages the amount of work in progress.

* Inspecting and Adapting the Workflow: Regularly reviewing and adjusting the workflow to improve efficiency and effectiveness

Answer : A

The Definition of Done (DoD) still applies even if policies are explicitly stated at each column of your workflow. The DoD is a fundamental concept in Scrum that ensures a shared understanding of what it means for work to be complete. Even with explicit policies at each stage of the workflow, the DoD provides a consistent standard for the team's deliverables, ensuring quality and alignment with stakeholder expectations

Answer : B

Little's Law establishes a relationship between three flow metrics: Work in Progress (WIP), Cycle Time, and Throughput. It provides insights into how changes in one metric affect the others in a stable system.

Little's Law is used to understand and manage flow within a system but is not a forecasting tool for output or future performance. It assumes a stable and predictable system where the input and output rates are consistent.

Why Not True?

Forecasting requires variability, historical data, and often different statistical models. While Little's Law supports system predictability and capacity planning, it does not directly project future Scrum Team outputs or delivery dates.

Thus, Little's Law helps teams analyze and optimize flow but is not used for forecasting.

Answer : D

In Professional Scrum with Kanban, the Work in Progress (WIP) limits are set as a policy to maintain a sustainable flow of work. Urgent work emerging does not automatically warrant changing these WIP limits; instead, the team should first discuss how to accommodate the urgent work within the existing constraints. Modifying WIP limits for urgent work could undermine the benefits of a controlled flow, which is why urgent work should not be a reason to change WIP limits during a Sprint

Answer : B, C

Kanban for Scrum Teams maximizes value delivered by:

1. Enabling Tighter Empirical Feedback Loops via Faster Cycle Times (Option B):

Kanban practices help Scrum Teams reduce Cycle Times, which is the time it takes for a work item to move from 'start' to 'finish.' Faster Cycle Times mean that feedback on work done is received more quickly, allowing the team to make necessary adjustments sooner. This rapid feedback loop enhances the empirical process control central to Scrum, thus ensuring that the team is always delivering value in line with the needs of stakeholders(

2. Optimizing the Flow of Value (Option C):

Kanban focuses on optimizing the flow of work through the team's process. This is achieved by limiting Work in Progress (WIP) and actively managing flow metrics such as throughput and cycle time. By optimizing flow, teams can ensure that work items are completed efficiently and effectively, minimizing waste and maximizing the delivery of value to the customer(

The other options are less accurate:

* Option A: Minimizing time spent in meetings/events is not the primary goal of Kanban; rather, it is about optimizing flow and value delivery.

* Option D: Minimizing transaction costs is more related to Lean principles, but it does not directly address the value delivered as effectively as options B and C.

* Option E: Choosing higher-value items to deliver is part of prioritization, which is more related to Product Backlog management than to Kanban's specific practices

Answer : A, D

1. The Kanban Board Provides Transparency (Option A):

A Kanban board visualizes the flow of work, making it easy for the Scrum Team to see the status of work items, identify bottlenecks, and inspect and adapt their processes. This visual transparency is a fundamental aspect of both Scrum and Kanban and supports the empirical process control central to Scrum(

2. Kanban Helps Achieve Faster, Healthier Flow (Option D):

By focusing on optimizing flow (e.g., reducing Cycle Time and managing Work in Progress), Kanban helps Scrum Teams achieve a faster, more predictable flow of work. This improvement in flow brings more rapid transparency, allowing for more effective inspection and adaptation during Scrum events such as the Daily Scrum, Sprint Review, and Sprint Retrospective(

Option B (Kanban metrics are used in the Sprint Review to allow the Product Owner to inspect Throughput and adapt the Scrum Team's Cycle Time) is not necessarily accurate, as the Sprint Review focuses on the product increment and stakeholder feedback, not directly on Kanban metrics.

Option C (Kanban helps Scrum Teams deal with simple and complicated work where empiricism is not necessary) is incorrect because both Kanban and Scrum rely on empiricism (transparency, inspection, and adaptation) to deal with work complexity

Answer : C

A probabilistic forecast is intended to communicate a prediction based on historical data, showing the likelihood of completing a certain amount of work within a given time frame. It helps the team and stakeholders understand the probability of meeting certain goals or deadlines based on past performance, supporting more informed decision-making