Scrum PSK-I Exam Dumps

When Developers limit Work in Progress (WIP) within a Sprint:

1. Developers Stop Beginning Work and Start Finishing Work (Option A):

Limiting WIP encourages the team to focus on completing work that has already been started rather than starting new tasks. This 'stop starting, start finishing' approach helps to reduce multitasking and ensures that tasks are completed more efficiently(

2. Self-management Strengthened Due to Increased Transparency (Option C):

Limiting WIP increases transparency by clearly showing what work is in progress and what remains to be done. This heightened visibility encourages the Developers to self-manage more effectively, as they can see what needs attention and make collective decisions about the next steps(

3. Increased Collaboration/Swarming Between Developers (Option D):

With a limited amount of work in progress, Developers are more likely to collaborate or 'swarm' on the tasks that are currently active. This can lead to faster completion of tasks, shared knowledge among team members, and a stronger sense of teamwork(

Option B (The amount of work done by the end of the Sprint would be reduced) is not necessarily correct. Limiting WIP does not inherently reduce the amount of work completed; instead, it aims to improve focus, reduce waste, and ensure more consistent delivery.

The Definition of Workflow should include policies that dictate how work flows through the system, such as Visualization policies, Pull policies, WIP Limits, Service Level Expectations, Work Item types, and the Definition of Done. These elements help the Scrum Team maintain transparency and consistency in their process, enhancing predictability and facilitating continuous improvement. Reference: The Kanban Guide for Scrum Teams.

Cycle Time in the context of Professional Scrum with Kanban is defined as the time it takes for a single work item to move from the start to the end of a specific process or workflow. This metric is crucial for understanding how efficiently a team can process individual work items through their defined workflow stages.

* Option A describes a broader measurement from the initial concept to customer feedback post-release. This could align more with the concept of Lead Time rather than Cycle Time.

* Option B correctly describes a possible measurement for Cycle Time --- the time a work item spends in one specific column (workflow stage). This is in line with the definitions provided in the Kanban Guide for Scrum Teams, where Cycle Time can measure time within distinct parts of the workflow.

* Option D accurately reflects the definition of Cycle Time, which measures the elapsed time from when work starts on an item until it is completed.

* Option C describes 'Throughput,' which is a measure of the number of items delivered over a specific time period (e.g., daily or weekly). This is not related to Cycle Time but is a separate flow metric often used alongside Cycle Time to understand team performance and capacity better(

Thus, Option C is the correct answer as it does not correctly describe Cycle Time. This explanation is verified with resources from Scrum.org that define Cycle Time within the scope of Professional Scrum with Kanban practices.

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

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.