Scrum PSK-I Exam Practice Test Instant Access

Question 1

Which of the following are Kanban practices for Scrum?

(choose the best answer)

AVisualizing flow, limiting WIP, actively managing the Work in Progress (WIP),
inspecting & adapting the Workflow.

BKaizen, remove delays, visualize policies, pull system.

CSmall batches, limit WIP, eliminate waste, Kaizen.

DClass of service, cost of delay, visualize the Workflow, limit WIP, manage flow.

ET-shirt size estimation, service level expectations, limit WIP.

Answer : A

The best answer is option A, which outlines the core Kanban practices for Scrum:

* Visualizing Flow: Helps the team see the state of work items at a glance.

* Limiting Work in Progress (WIP): Prevents overloading the team and promotes focus on completing work.

* Actively Managing the WIP: Ensures the team continuously monitors and manages the amount of work in progress.

* Inspecting and Adapting the Workflow: Regularly reviewing and adjusting the workflow to improve efficiency and effectiveness

Question 2

What might a Scrum Team visualize with Kanban?

(choose the best three answers)

AThe Product Backlog.

BThe Sprint Retrospective.

CThe Sprint Backlog.

DThe Definition of Done.

Answer : A, C, D

When a Scrum Team uses Kanban, they can visualize:

* The Product Backlog: By making the Product Backlog visible, the team can track what work items are upcoming and prioritize them effectively.

* The Sprint Backlog: Visualizing the Sprint Backlog helps the team see the work planned for the current Sprint, track progress, and manage flow.

* The Definition of Done: Making the Definition of Done visible ensures that all team members and stakeholders understand the criteria that must be met for work to be considered complete

Question 3

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

(choose the best answer)

AShorter feedback cycles.

BMore sustainable pace of work.

CFaster realization of value.

DImproved collaboration.

EAll of the answers.

Answer : E

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.

Question 4

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)

AAdd the urgent item to their Sprint Backlog but only start working on it when their
WIP Limits allow it.

BAdjust the WIP Limits to allow for taking on the extra item and record it as part of
their Definition of Workflow.

CTake on the urgent item as an exception to the WIP Limits and visualize that
they are above their WIP Limit.

DReject the urgent item since the WIP Limits do not allow it. Tell the Product
Owner to wait until the next Sprint.

Answer : A, C

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.

Question 5

What are possible benefits of supplementing Scrum with Kanban practices?

(choose the best four answers)

AMay result in greater collaboration within the Scrum Team.

BScrum Teams no longer need the Sprint time box.

CMay reduce the average Cycle Time.

DIntroduces better transparency into state of Work in
Progress (WIP).

EMay help to discover areas of variability within your Sprint.

FRemoves the need for the Sprint Planning event.

GAllows teams to release multiple times a Sprint.

Answer : A, C, D, E

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

Question 6

True or False: Work Item Age is a leading indicator for the length of the Scrum Team's

feedback loop for that (in progress) item.

ATrue

BFalse

Answer : A

Work Item Age is the amount of time a work item has been in progress. It acts as a leading indicator for the length of the Scrum Team's feedback loop for that item. If a work item stays in progress for too long, it indicates that feedback is delayed, potentially impacting the team's ability to adapt and respond effectively. Tracking Work Item Age helps the team monitor flow and take timely actions to ensure that feedback loops remain short and effective

Question 7

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)

AAny refined Product Backlog item in the Product Backlog is WIP.

BHow it is defined and who within the Scrum Team defines it depends on the
boundaries and scope of the Definition of Workflow.

CAny Product Backlog item in the Sprint Backlog is a WIP.

DIn any way the Scrum Team chooses to define it.

EHowever the Developers want. They have the final say on the Sprint Backlog.

Answer : B

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.

Scrum PSK-I Professional Scrum with Kanban Exam Practice Test