Scrum PSK-I Exam Dumps

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

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. Reference: 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

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.

While WIP is a crucial metric for Kanban teams, it is not a flow metric. Flow metrics measure the movement of work through the system, while WIP measures the amount of work currently in progress.

Here's a breakdown of the other options:

Cycle Time: The time it takes to complete a piece of work from start to finish.

Throughput: The rate at which work is completed.

Work item age: The amount of time a work item has spent in the system.

All of these metrics provide insights into the flow of work and can be used to identify bottlenecks and optimize the workflow.

Therefore, option B, 'Work in Progress (WIP),' is the correct answer.