PSK-I Sample Questions Answers

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

An SLE indicates the expected time frame within which work items should be completed, expressed as a percentage probability over a specific range of days. This helps Scrum Teams using Kanban to establish realistic expectations about delivery timelines. References: The Kanban Guide for Scrum Teams​.

The Definition of Done (DoD) still applies even if policies are explicitly stated at each column of your workflow. The DoD is a fundamental concept in Scrum that ensures a shared understanding of what it means for work to be complete. Even with explicit policies at each stage of the workflow, the DoD provides a consistent standard for the team's deliverables, ensuring quality and alignment with stakeholder expectations

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.

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.

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

During the Sprint Retrospective, once a team decides to supplement their Scrum with Kanban, all the mentioned elements might be considered:

•Workflow: To ensure it aligns with Kanban practices.

•Current policies: To review and adapt any team policies that may need to change.

•WIP Limit: To set appropriate limits to enhance flow.

•Metrics and charts (e.g., Cumulative Flow Diagram, Cycle Time Scatterplot, Work Item Aging): To visualize flow, identify bottlenecks, and make data-driven decisions for continuous improvement.

Considering all these elements helps the Scrum Team integrate Kanban practices effectively into their existing Scrum framework

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​​.

The Definition of Workflow should include policies that dictate how work flows through the system, such as Visualization policies, Pull policies, WIP Limits, Service Level Expectations, Work Item types, and the Definition of Done. These elements help the Scrum Team maintain transparency and consistency in their process, enhancing predictability and facilitating continuous improvement. References: The Kanban Guide for Scrum Teams​​.

Cycle Time is a lagging indicator, meaning it can only be measured after a work item is complete. Therefore, it cannot be used as a leading indicator of the length of the feedback loop (Option A). Additionally, Cycle Time is not typically used during the Daily Scrum to help Developers inspect and adapt their Sprint; rather, it is more often used to assess overall process efficiency

During Sprint Planning, the most relevant metric to consider is Throughput (Option B), which measures the number of work items completed in a given time frame (e.g., per Sprint). By reviewing past throughput, the team can make informed decisions about how much work they are likely to complete in the upcoming Sprint, taking into account their capacity and any potential changes in team composition or external factors.

•Service Level Expectation (A) is less relevant as it is more about setting expectations with stakeholders rather than planning the Sprint.

•Work Item Aging (C) is a leading indicator metric used to track how long current work items have been in progress, which is less helpful during planning.

•Work in Progress (D) indicates the current workload but does not provide historical data useful for forecasting in Sprint Planning

The Scrum framework contains elements that can be treated as explicit policies. For example, Scrum defines specific roles, events, and artifacts, which are treated as rules or guidelines that the team must follow to maintain Scrum's framework. In the context of Scrum with Kanban, additional explicit policies, such as Work in Progress (WIP) limits, may also be established to further optimize flow

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

Kanban emphasizes explicit policies for better transparency and alignment, and elements such as the Definition of Done, Definition of Ready, and Product Backlog refinement can be utilized as explicit policies to clarify the Scrum Team’s working agreements. These policies help the team make consistent decisions and streamline their processes. References: The Kanban Guide for Scrum Teams and The Scrum Guide​​.

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.

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.