CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Scrum
  5. PSK-I

Free PSK-I Exam Braindumps (page: 5)

Page 4 of 18
PDF with 73 Questions

Who must change the Work in Progress (WIP) Limits in the Definition of Workflow when urgent work emerges from the Sprint?

(choose the best answer)

  1. The Developers.
  2. The Product Owner.
  3. The Scrum Master.
  4. No one. Urgent work is not a reason to change WIP Limits.
  5. No one. WIP Limits cannot be modified during a Sprint.

Answer(s): D

Explanation:

In Professional Scrum with Kanban, the Work in Progress (WIP) limits are set as a policy to maintain a sustainable flow of work. Urgent work emerging does not automatically warrant changing these WIP limits; instead, the team should first discuss how to accommodate the urgent work within the existing constraints. Modifying WIP limits for urgent work could undermine the benefits of a controlled flow, which is why urgent work should not be a reason to change WIP limits during a

Sprint



True or False: If you reduce your batch size, your overall efficiency will always increase.

  1. True
  2. False

Answer(s): B

Explanation:

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



When can a Work in Progress (WIP) Limit change?

(choose the best answer)

  1. At any time.
  2. When the Product Owner decides to change it.
  3. It never changes.
  4. Only during the Sprint Retrospective.
  5. Only during Sprint Planning.
  6. Only during the Daily Scrum.

Answer(s): D

Explanation:

According to the Kanban Guide for Scrum Teams, Work in Progress (WIP) limits are set to control the amount of work in progress in a system, enhancing flow, reducing bottlenecks, and ensuring smoother delivery. WIP limits can be changed as a result of an inspection and adaptation cycle, which primarily occurs during the Sprint Retrospective.

During the Sprint Retrospective, the Scrum Team reflects on its process, practices, and interactions. This is the time when the team inspects its flow, evaluates the effectiveness of the current WIP limits, and can make decisions to adjust them based on observed issues or potential improvements. The goal is to optimize the team's ability to deliver value, and adjusting WIP limits during the Retrospective allows for thoughtful consideration based on the team's experience and data from the completed Sprint.

Changing WIP limits at other times could disrupt the flow and reduce the predictability and stability that the limits are intended to create. Therefore, the best practice is to evaluate and change them during the Sprint Retrospective, where the team can inspect the results of their workflow and make informed decisions for the upcoming Sprints



A Scrum Team's Definition of Workflow must have defined points at which the Scrum Team considers work to have started and to have finished. This allows the team to track their Work in

Progress (WIP). How are these points defined?

(choose the best answer)

  1. Any refined Product Backlog item in the Product Backlog is WIP.
  2. How it is defined and who within the Scrum Team defines it depends on the boundaries and scope of the Definition of Workflow.
  3. Any Product Backlog item in the Sprint Backlog is a WIP.
  4. In any way the Scrum Team chooses to define it.
  5. However the Developers want. They have the final say on the Sprint Backlog.

Answer(s): B

Explanation:

The Definition of Workflow includes the agreed-upon points at which the Scrum Team considers work to have started and finished. These points are determined based on the boundaries and scope of the team's workflow. This definition must be clearly understood by the entire team to track Work in

Progress (WIP) effectively and manage flow efficiently. It is up to the Scrum Team to define these boundaries to suit their specific context and workflow needs.






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

PSK-I Discussions & Posts