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: 3)

Page 2 of 18
PDF with 73 Questions

For a specific Sprint Backlog item that has been started, what is the best chart (analytic) to determine when it will be finished?

(choose the best answer)

  1. Throughput Run Chart.
  2. Cumulative Flow diagram (CFD).
  3. Work Item Aging Chart.
  4. Control chart.

Answer(s): C

Explanation:

The Work Item Aging Chart is the best chart to determine when a specific Sprint Backlog item that has been started will be finished. This chart provides a visual representation of how long each work item has been in progress, without being completed. It focuses on items that are currently active and helps teams identify which items are aging too much in the workflow, which might require attention to ensure they are completed promptly. The Work Item Aging Chart helps to quickly identify items that might be taking longer than expected, making it ideal for forecasting when a started item will be finished



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.






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

PSK-I Discussions & Posts