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

Page 6 of 18
PDF with 73 Questions

What are possible benefits of supplementing Scrum with Kanban practices?

(choose the best four answers)

  1. May result in greater collaboration within the Scrum Team.
  2. Scrum Teams no longer need the Sprint time box.
  3. May reduce the average Cycle Time.
  4. Introduces better transparency into state of Work in
    Progress (WIP).
  5. May help to discover areas of variability within your Sprint.
  6. Removes the need for the Sprint Planning event.
  7. Allows teams to release multiple times a Sprint.

Answer(s): A,C,D,E

Explanation:

Supplementing Scrum with Kanban practices can bring several benefits to a Scrum Team:

· Greater Collaboration (A): By using Kanban practices like visualizing work and managing flow, team members have clearer visibility into each other's tasks, fostering better collaboration.

· Reduced Average Cycle Time (C): Kanban's focus on flow and limiting WIP helps decrease the time it takes for items to move from start to finish.

· Better Transparency (D): Kanban practices enhance visibility into the current state of work, making it easier to identify bottlenecks and areas for improvement.

· Discover Areas of Variability (E): The use of flow metrics such as cycle time and throughput in Kanban can help identify variability in processes, enabling the team to make adjustments for more predictable delivery



A service level expectation (SLE) consists of which two items?

(choose the best two answers)

  1. A cost of delay.
  2. A probability.
  3. A forecasted date.
  4. A period of elapsed days.

Answer(s): B,D

Explanation:

A Service Level Expectation (SLE) in Kanban provides an agreement or expectation regarding the time it will take to complete a work item. An SLE consists of two main elements:

1. A probability (Option B): This is the likelihood or confidence level (e.g., 85%) that a work item will be completed within the specified period.

2. A period of elapsed days (Option D): This defines the maximum amount of time (e.g., 10 days) expected for a work item to be completed. The combination of these two elements helps set clear expectations and guide planning and forecasting efforts(

Options A (A cost of delay) and C (A forecasted date) are not part of the standard elements defining an SLE. The cost of delay is a concept related to prioritization, and a forecasted date is usually derived from the SLE but is not part of it.



What should the Developers do if, during the Sprint, the Product Owner asks them to add an urgent unplanned work item that aligns to the Sprint Goal but does not fit into the current Work in Progress (WIP) Limits?

(choose the two best answers)

  1. Add the urgent item to their Sprint Backlog but only start working on it when their WIP Limits allow it.
  2. Adjust the WIP Limits to allow for taking on the extra item and record it as part of their Definition of Workflow.
  3. Take on the urgent item as an exception to the WIP Limits and visualize that they are above their WIP Limit.
  4. Reject the urgent item since the WIP Limits do not allow it. Tell the Product Owner to wait until the next Sprint.

Answer(s): A,C

Explanation:

If the Product Owner requests that an urgent, unplanned work item be added during the Sprint, and it aligns with the Sprint Goal but does not fit within the current WIP limits, the Developers should:

1. Add the urgent item to their Sprint Backlog but only start working on it when their WIP Limits allow it (Option A): This maintains the integrity of the WIP limits and ensures that the team doesn't overcommit or create too much work in progress, which could affect flow and focus.

2. Take on the urgent item as an exception to the WIP Limits and visualize that they are above their WIP Limit (Option C): By taking on the urgent item as an exception, the team can address the urgency while being transparent about the temporary breach of the WIP limits. This visualization helps the team and stakeholders understand the current state of work and its impact(

Options B (Adjust the WIP Limits) and D (Reject the urgent item) are less suitable because they either undermine the WIP control mechanism or fail to accommodate a potentially critical change that aligns with the Sprint Goal.



What is the potential benefit of limiting Work in Progress (WIP)?

(choose the best answer)

  1. Shorter feedback cycles.
  2. More sustainable pace of work.
  3. Faster realization of value.
  4. Improved collaboration.
  5. All of the answers.

Answer(s): E

Explanation:

Limiting Work in Progress (WIP) has several potential benefits for a Scrum Team, including:

1. Shorter feedback cycles (Option A): By limiting the amount of work in progress, the team can focus on completing work faster, which leads to shorter feedback loops and quicker validation of hypotheses or deliverables.

2. More sustainable pace of work (Option B): Limiting WIP helps prevent overburdening the team, promoting a more balanced and sustainable work pace.

3. Faster realization of value (Option C): By completing items more quickly and reducing multitasking, the team delivers value faster to stakeholders.

4. Improved collaboration (Option D): When WIP is limited, team members are more likely to collaborate to finish tasks that are already in progress rather than starting new ones.






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

PSK-I Discussions & Posts