Scrum PSK-I Professional Scrum with Kanban Exam Practice Test

Answer : D

Scrum Teams using Kanban can start to increase predictability by reducing the amount of work in progress (WIP) through WIP limits. This approach helps to limit the number of items being worked on at any given time, thus reducing multitasking and context switching. It allows the team to focus on completing a few items before starting new ones, which directly impacts the flow of work and helps to predict when items will be completed. By controlling the WIP, teams can achieve a steady flow of work, improve cycle times, and make more reliable forecasts about future deliveries

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 : D

The Service Level Expectation (SLE) provides the most benefit during the Daily Scrum. This is because the Daily Scrum is focused on inspecting the progress towards the Sprint Goal and adapting the plan to optimize the flow of work for the day. The SLE helps the Scrum Team understand if work items are on track to be completed within the expected time frames. If the actual cycle times are exceeding the SLE, the team can discuss and make adjustments during the Daily Scrum to address any impediments or to rebalance work, thereby maintaining a steady flow.

By using the SLE in the Daily Scrum, the team gets a daily, empirical measure of their workflow, allowing them to make quick decisions to keep work moving smoothly and predictably. This aligns well with the goal of the Daily Scrum, which is to ensure that the team is on track to achieve the Sprint Goal by the end of the Sprint(

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 : A

Work Item Age is the amount of time a work item has been in progress. It acts as a leading indicator for the length of the Scrum Team's feedback loop for that item. If a work item stays in progress for too long, it indicates that feedback is delayed, potentially impacting the team's ability to adapt and respond effectively. Tracking Work Item Age helps the team monitor flow and take timely actions to ensure that feedback loops remain short and effective

Answer : A, C, D

When a Scrum Team uses Kanban, they can visualize:

* The Product Backlog: By making the Product Backlog visible, the team can track what work items are upcoming and prioritize them effectively.

* The Sprint Backlog: Visualizing the Sprint Backlog helps the team see the work planned for the current Sprint, track progress, and manage flow.

* The Definition of Done: Making the Definition of Done visible ensures that all team members and stakeholders understand the criteria that must be met for work to be considered complete