Scrum PSK-I Exam Questions
Professional Scrum with Kanban (Page 5 )

Updated On: 5-Mar-2026

What is true about the Sprint Goal if the Developers reserve capacity for unplanned work during an upcoming sprint?

(choose the best answer)

  1. The Sprint Goal no longer helps the Developers. They do not know what they will be working on.
  2. The Developers should never reserve more than 5% capacity for unplanned work. It is inefficient if the Developer's forecast does not take into account all of their capacity.
  3. The Sprint Goal becomes more important. It can help the Developers maintain their focus as new Product Backlog items are brought into the Sprint Backlog.

Answer(s): C

Explanation:

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



Scrum Teams using Kanban can start to increase predictability by:

(choose the best answer)

  1. Visualizing the Workflow using a Kanban board.
  2. Improving transparency by having a CFD, Control Chart and Aging chart.
  3. Inspecting and adapting the Product Backlog during the Sprint Review.
  4. Reducing the amount of work in progress by introducing Work in Progress (WIP) Limits.

Answer(s): D

Explanation:

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



When the Developers limit Work in Progress (WIP) inside a Sprint, what would you expect to observe?

(choose the best three answers)

  1. The Developers would stop beginning work, and instead, start finishing work.
  2. The amount of work done by the end of the Sprint would be reduced.
  3. Self-management would be strengthened as a result of increased transparency.
  4. Increased collaboration/swarming between the Developers.

Answer(s): A,C,D

Explanation:

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.



True or False: Little's Law is used to forecast a Scrum Team's output.

  1. True
  2. False

Answer(s): A

Explanation:

Little's Law is a mathematical formula used in queueing theory and Kanban to relate the average number of items in a system (Work in Progress), the average completion rate (Throughput), and the average time an item spends in the system (Cycle Time). In the context of Scrum Teams using Kanban, Little's Law can be used to forecast a team's output by understanding the relationship between these variables(

Thus, it is True that Little's Law can be used to forecast a Scrum Team's output, assuming that the underlying assumptions of Little's Law (such as a stable system and consistent flow) are met.



Which of these statements are true about Kanban and the Scrum theory of empiricism?

(choose the best two answers)

  1. The Kanban board provides Scrum Teams with transparency that helps them inspect and adapt their process.
  2. Kanban metrics are used in the Sprint Review to allow the Product Owner to inspect the Throughput and adapt the Scrum Team's Cycle Time.
  3. Kanban helps Scrum Teams deal with simple and complicated work where empiricism is not necessary.
  4. Kanban helps Scrum Teams achieve faster, healthier flow. That brings more rapid transparency about the product, enabling a more effective inspection and adaptation loop.

Answer(s): A,D

Explanation:

1. The Kanban Board Provides Transparency (Option A):

A Kanban board visualizes the flow of work, making it easy for the Scrum Team to see the status of work items, identify bottlenecks, and inspect and adapt their processes. This visual transparency is a fundamental aspect of both Scrum and Kanban and supports the empirical process control central to Scrum(

2. Kanban Helps Achieve Faster, Healthier Flow (Option D):

By focusing on optimizing flow (e.g., reducing Cycle Time and managing Work in Progress), Kanban helps Scrum Teams achieve a faster, more predictable flow of work. This improvement in flow brings more rapid transparency, allowing for more effective inspection and adaptation during Scrum events such as the Daily Scrum, Sprint Review, and Sprint Retrospective(

Option B (Kanban metrics are used in the Sprint Review to allow the Product Owner to inspect Throughput and adapt the Scrum Team's Cycle Time) is not necessarily accurate, as the Sprint Review focuses on the product increment and stakeholder feedback, not directly on Kanban metrics.

Option C (Kanban helps Scrum Teams deal with simple and complicated work where empiricism is not necessary) is incorrect because both Kanban and Scrum rely on empiricism (transparency, inspection, and adaptation) to deal with work complexity



Viewing page 5 of 15
Viewing questions 21 - 25 out of 73 questions



Post your Comments and Discuss Scrum PSK-I exam dumps with other Community members:

PSK-I Exam Discussions & Posts

AI Tutor