Scrum Professional Scrum with Kanban PSK-I Exam Questions

Answer : C

When Developers reserve capacity for unplanned work during a Sprint, the Sprint Goal becomes even more crucial. It serves as the guiding objective that aligns the team's focus amidst uncertainties or when unplanned work is introduced. By having a clear Sprint Goal, the Developers can ensure that any new items brought into the Sprint Backlog still align with the overarching objective of the Sprint, helping them maintain focus and coherence in their efforts throughout the Sprint

Answer : B

Reducing batch size does not always guarantee an increase in overall efficiency. While smaller batch sizes can lead to faster feedback, more frequent deliveries, and reduced risk, there can be situations where reducing the batch size too much results in inefficiencies, such as increased overhead costs or excessive context switching. Thus, the relationship between batch size and efficiency depends on the context, system constraints, and the nature of the work

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

The Scrum framework contains elements that can be treated as explicit policies. For example, Scrum defines specific roles, events, and artifacts, which are treated as rules or guidelines that the team must follow to maintain Scrum's framework. In the context of Scrum with Kanban, additional explicit policies, such as Work in Progress (WIP) limits, may also be established to further optimize flow

Answer : B

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

Answer : A, C, D

Professional Scrum with Kanban builds upon the core Scrum values to enhance flow and effectiveness within the team. The relevant values are:

* Courage: Encourages team members to address issues, experiment with changes in the workflow, and make adjustments transparently, even when facing uncertainty.

* Focus: Enhances the team's ability to concentrate on achieving the Sprint Goal and flow of work items by using Work in Progress (WIP) limits and other Kanban practices.

* Openness: Promotes an open environment where the team transparently shares information on work progress, obstacles, and opportunities for improvement, which is key for continuous inspection and adaptation in Kanban.

These values directly support the empirical process control and continuous improvement principles of Kanban

Answer : B

Little's Law establishes a relationship between three flow metrics: Work in Progress (WIP), Cycle Time, and Throughput. It provides insights into how changes in one metric affect the others in a stable system.

Little's Law is used to understand and manage flow within a system but is not a forecasting tool for output or future performance. It assumes a stable and predictable system where the input and output rates are consistent.

Why Not True?

Forecasting requires variability, historical data, and often different statistical models. While Little's Law supports system predictability and capacity planning, it does not directly project future Scrum Team outputs or delivery dates.

Thus, Little's Law helps teams analyze and optimize flow but is not used for forecasting.