Free Practice Questions for Scrum PSK-I Exam

While refining the Product Backlog is essential in Scrum, it is not an essential component specifically for achieving flow in Kanban practices. Achieving flow requires visualizing the workflow, limiting WIP, actively managing WIP, and continuously inspecting and adapting the workflow. Frequent Product Backlog refinement helps with the overall Scrum framework but is not directly tied to the initial goal of achieving flow in a Kanban system

The Scrum framework already contains elements that create a pull system. In Scrum, the team members "pull" work into the Sprint Backlog during Sprint Planning. They decide which Product Backlog items they will commit to completing based on their capacity and the Sprint Goal. This is a form of a pull system where the team only takes in as much work as they believe they can complete within a Sprint, aligning with Kanban principles that limit Work in Progress (WIP) to optimize flow

Adjusting WIP limits can directly impact Cycle Time and overall flow by reducing bottlenecks and increasing focus. Lowering WIP can enhance the team’s ability to complete work within a Sprint by minimizing task switching and promoting faster delivery of value. References: The Kanban Guide for Scrum Teams​​.

Even when using Kanban, Scrum Teams still follow the Scrum framework, which mandates crafting a Sprint Goal during Sprint Planning. The Sprint Goal provides focus and alignment for the team, ensuring that all work contributes toward a common objective, rather than being taken on as needed. References: The Scrum Guide​.

Little's Law is a formula used to understand the relationship between system throughput, work-in-progress (WIP), and lead time. While it can be used to analyze and optimize the flow of work, it is not specifically designed for forecasting a Scrum Team's output.

Scrum Teams typically use techniques like story point estimation and historical velocity to forecast their output.

The four key flow metrics in Scrum with Kanban are:

•Work in Progress (WIP): The number of items that are currently being worked on.

•Work Item Age: The time that has elapsed since an item started, which helps identify aging work that may need attention.

•Throughput: The number of items completed over a specific period, helping to measure productivity.

•Cycle Time: The total time from when an item starts until it is finished, used to assess how quickly items are moving through the process.

These metrics are essential for understanding and optimizing the flow of work in a Scrum team using Kanban practices

When Developers add Kanban to Scrum, the way they use the Sprint Goal during their Daily Scrum can change. In traditional Scrum, the Sprint Goal is a shared commitment for the Sprint. However, in Professional Scrum with Kanban, the focus shifts to the flow of work and delivering value incrementally.

While the Sprint Goal still provides direction, the Daily Scrum may involve discussions about:

Progress towards the Sprint Goal:How are we progressing towards the overall goal?

Work in Progress (WIP):Are we adhering to WIP limits?

Blockers and impediments:What is preventing the team from progressing?

Prioritization:Are we working on the highest-value items?

By focusing on these aspects, the team can ensure that they are delivering value continuously and efficiently.

Sprints remain a core aspect of the Scrum framework, regardless of the use of Kanban. Sprints provide a time-boxed cadence and structure that is integral to Scrum. The addition of Kanban practices enhances Scrum but does not replace the need for Sprints. References: The Kanban Guide for Scrum Teams​.

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.