Scrum Professional Scrum with Kanban PSK-I Exam Questions

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

Answer : A, B

During a flow-based Daily Scrum, the team is likely to review metrics such as Work Item Age and Work in Progress (WIP):

* Work Item Age: Helps to identify items that have been in progress for a longer time than expected, signaling possible impediments or the need for swarming to complete those items.

* Work in Progress (WIP): Indicates the number of items currently being worked on, ensuring that the team is not exceeding the agreed WIP limits, which is crucial for maintaining a steady flow

Answer : E

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

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.

Answer : D

In the context of Professional Scrum with Kanban, the Sprint Retrospective is the most suitable time to inspect and adapt WIP Limits. This is because the Retrospective is a dedicated time-box for the Scrum Team to reflect on its performance and identify areas for improvement.

Here's why:

Continuous Improvement: The Retrospective is a key part of the Scrum framework, designed to foster continuous improvement. By reviewing WIP Limits during this time, the team can assess their effectiveness and make data-driven decisions.

Data-Driven Decisions: By tracking WIP Limits over time, the team can gather valuable insights into their workflow and identify bottlenecks. This data can inform decisions about adjusting WIP Limits to optimize flow and productivity.

Team Collaboration: The Retrospective provides an opportunity for the entire team to discuss and agree upon changes to WIP Limits. This collaborative approach ensures buy-in and commitment from all team members.

While it's true that Developers can monitor WIP Limits throughout the Sprint, the Retrospective is the designated time for a formal review and adjustment. This ensures that any changes are aligned with the team's overall goals and strategy.

Answer : A, B, D

Lagging indicator metrics are metrics that provide information about past performance:

1. Velocity (Option A): This is a measure of the amount of work a Scrum Team completes in a Sprint. It is a lagging indicator because it reflects what has been done rather than predicting future performance.

2. Cycle Time (Option B): This metric measures the time taken to complete a work item from start to finish. It is a lagging indicator because it provides data on how long work items took to complete in the past.

3. Throughput (Option D): This refers to the number of work items completed in a given period. Like Velocity, it reflects past performance and is considered a lagging indicator.

Work in Progress (Option C) and Work Item Aging (Option E) are not lagging indicators:

* Work in Progress (C): is a current state metric that indicates how much work is currently in progress.

* Work Item Aging (E): is a leading indicator, providing insights into how long a work item has been in progress, helping predict delays or bottlenecks

Answer : D

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