Scrum Professional Scrum with Kanban PSK-I Exam Questions

Answer : D

The four key flow metrics in Scrum with Kanban are:

* Work in Progress (WIP): The number of items that are currently being worked on.

* Work Item Age: The time that has elapsed since an item started, which helps identify aging work that may need attention.

* Throughput: The number of items completed over a specific period, helping to measure productivity.

* Cycle Time: The total time from when an item starts until it is finished, used to assess how quickly items are moving through the process.

These metrics are essential for understanding and optimizing the flow of work in a Scrum team using Kanban practices

Answer : D

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.

Answer : A

Work in Progress (WIP) Limits can be adjusted at any time as needed to optimize flow and improve the system's efficiency. The decision to adjust WIP limits is typically informed by the team's observations of flow metrics (e.g., Cycle Time, Throughput, and Work Item Age) or to address bottlenecks or inefficiencies.

Supporting Reasons:

Kanban's Flexibility:

Unlike rigid frameworks, Kanban allows for flexibility in changing WIP limits whenever necessary to adapt to evolving conditions.

Scrum Events:

Adjustments to WIP limits are often discussed during events like the Sprint Retrospective or Daily Scrum, but these are not the only times changes can be made.

Empirical Process Control:

Teams use transparency, inspection, and adaptation to decide when to change WIP limits based on real-time needs.

Why Not the Other Options?

B . When the Product Owner decides to change it:

Incorrect. WIP limits are a team decision and are not controlled solely by the Product Owner.

C . It never changes:

Incorrect. WIP limits are not static; they are dynamic and evolve based on team and system needs.

D . Only during the Sprint Retrospective:

Incorrect. While the Sprint Retrospective is a common time to discuss adjustments, changes are not restricted to this event.

E . Only during Sprint Planning:

Incorrect. Sprint Planning focuses on selecting work for the Sprint, not exclusively on adjusting WIP limits.

F . Only during the Daily Scrum:

Incorrect. Adjustments can be made during the Daily Scrum but are not limited to this event.

Adjusting WIP limits at any time ensures the team maintains an optimal flow, a core principle of The Kanban Guide for Scrum Teams.

Answer : B, D

1. WIP Limits provide a boundary/container in which the Scrum Team self-manages (Option B):

WIP Limits establish clear boundaries within which the Scrum Team can make decisions about how much work they take on. This framework allows the team to self-manage their workflow more effectively, as they must decide collectively how to stay within these limits while delivering value.

2. As part of self-managing, Scrum Teams figure out their own WIP Limits (Option D):

A fundamental principle of Scrum is self-management. The team collectively decides its WIP limits, adjusting them based on empirical evidence and ongoing learning about their capacity, flow, and delivery capabilities. This decision-making process is a key aspect of the team's autonomy and self-management(

Options A and C are incorrect because WIP limits do not inhibit self-management (A); instead, they enable it. Additionally, a Scrum Master does not define WIP limits (C); the Scrum Team decides them.

Answer : B

Kanban does not eliminate the need for a Scrum Master when used with Scrum. The Scrum Master remains an essential role to facilitate the Scrum framework, help the team adopt both Scrum and Kanban practices effectively, and ensure the team understands and adheres to Scrum principles.

The role of the Scrum Master includes coaching the team on both Scrum and Kanban practices, removing impediments, and promoting continuous improvement. Therefore, even when Scrum is used with Kanban, the Scrum Master is not optional but a critical role in ensuring that the integration of these practices is successful(

Answer : B

The Definition of Workflow includes the agreed-upon points at which the Scrum Team considers work to have started and finished. These points are determined based on the boundaries and scope of the team's workflow. This definition must be clearly understood by the entire team to track Work in Progress (WIP) effectively and manage flow efficiently. It is up to the Scrum Team to define these boundaries to suit their specific context and workflow needs.

Answer : C

You always need a Scrum Master when applying Kanban practices in the Scrum framework. The role of the Scrum Master remains crucial, even when Kanban practices are incorporated, as they are responsible for ensuring that the Scrum framework is followed, including all the new practices introduced by Kanban. The Scrum Master helps facilitate the team's understanding and use of flow-based metrics and practices while maintaining the integrity of Scrum events, roles, and artifacts