Scrum Updated PSK-I Exam Questions and Answers by jimmy

Cycle Time is a lagging indicator, meaning it can only be measured after a work item is complete. Therefore, it cannot be used as a leading indicator of the length of the feedback loop (Option A). Additionally, Cycle Time is not typically used during the Daily Scrum to help Developers inspect and adapt their Sprint; rather, it is more often used to assess overall process efficiency

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.

Kanban is:

•A strategy for optimizing the flow of value through a process (Option B): Kanban focuses on improving flow and efficiency by using a visual pull system with limited WIP. This strategy helps teams balance demand against throughput and enhance productivity by limiting the number of work items in progress.

Options A (methodology for visualizing workflow) and C (set of practices additive to Scrum) are partially correct but do not fully capture Kanban's purpose. Kanban is not just a visualization tool (A), and while it can be additive to Scrum (C), it is fundamentally a flow-based strategy

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 steadyflow of work, improve cycle times, and make more reliable forecasts about future deliveries