PSK-I Exam Questions & Answers

Work in Progress (WIP) and Work Item Aging are considered leading indicator metrics in Scrum with Kanban. Leading indicators are metrics that provide information that can help predict future outcomes or performance.

* Work in Progress (WIP): This metric indicates the number of work items currently being worked on and can provide early signals about potential bottlenecks or issues in the workflow. Managing WIP effectively can help teams optimize their flow and predict how work might proceed in the future.

* Work Item Aging: This metric shows how long work items have been in progress without being completed. It provides an early indication of delays and can help teams identify items that might need attention to maintain a steady flow

A Cycle Time Scatterplot is a visualization tool used to display the cycle times for individual work items over time. This scatterplot provides several types of qualitative information:

1. General Cycle Time Trends (Option A): The scatterplot can show general trends over time, such as whether the cycle times are decreasing, increasing, or staying stable. This helps teams understand the overall direction in which their workflow efficiency is moving.

2. Single Cycle Time Outliers (Option B): The scatterplot also helps identify individual outliers --- work items that took significantly longer or shorter than usual to complete. These outliers can be further investigated to understand why they occurred and to prevent similar situations in the future.

3. Clusters of Cycle Time Outliers (Option C): In addition to single outliers, the scatterplot may reveal clusters of outliers. These clusters can indicate systemic issues, such as bottlenecks or recurring problems in a specific part of the process.

Since a Cycle Time Scatterplot provides all these types of information (general trends, single outliers, and clusters of outliers), the correct answer is D.

Work in Progress (WIP) Limits can be adjusted at any time as needed to optimize flow and improve the system's efficiency. The decision to adjust WIP limits is typically informed by the team's observations of flow metrics (e.g., Cycle Time, Throughput, and Work Item Age) or to address bottlenecks or inefficiencies.

Supporting Reasons:

Kanban's Flexibility:

Unlike rigid frameworks, Kanban allows for flexibility in changing WIP limits whenever necessary to adapt to evolving conditions.

Scrum Events:

Adjustments to WIP limits are often discussed during events like the Sprint Retrospective or Daily Scrum, but these are not the only times changes can be made.

Empirical Process Control:

Teams use transparency, inspection, and adaptation to decide when to change WIP limits based on real-time needs.

Why Not the Other Options?

B . When the Product Owner decides to change it:

Incorrect. WIP limits are a team decision and are not controlled solely by the Product Owner.

C . It never changes:

Incorrect. WIP limits are not static; they are dynamic and evolve based on team and system needs.

D . Only during the Sprint Retrospective:

Incorrect. While the Sprint Retrospective is a common time to discuss adjustments, changes are not restricted to this event.

E . Only during Sprint Planning:

Incorrect. Sprint Planning focuses on selecting work for the Sprint, not exclusively on adjusting WIP limits.

F . Only during the Daily Scrum:

Incorrect. Adjustments can be made during the Daily Scrum but are not limited to this event.

Adjusting WIP limits at any time ensures the team maintains an optimal flow, a core principle of The Kanban Guide for Scrum Teams.

A cumulative flow diagram (CFD) provides insights into the amount of WIP and helps track Cycle Time by showing how long items stay in each stage of the workflow. This visualization tool is valuable for teams using Scrum with Kanban as it highlights bottlenecks and helps manage flow through the stages of the workflow. Reference: The Kanban Guide for Scrum Teams.

The Kanban Guide for Scrum Teams outlines four primary Kanban practices essential for Scrum Teams:

Visualization of the Workflow.

Limiting Work in Progress (WIP).

Active management of work items in progress.

Explicit policies for workflow management, often including the identification of bottlenecks.

Inspecting and adapting the workflow is not explicitly listed as a Kanban practice for Scrum Teams. While inspection and adaptation are fundamental to Scrum (due to its reliance on empiricism), they are not specific to the set of Kanban practices integrated into Scrum.