PSK-I Exam Dumps and Practice Questions

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

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

Supplementing Scrum with Kanban practices encourages team collaboration and swarming. Kanban practices such as visualizing the workflow, limiting WIP, and focusing on flow metrics foster an environment where team members are more likely to collaborate closely to resolve bottlenecks and ensure a steady flow of work. This collaboration, often called 'swarming,' involves team members working together on fewer items to complete them faster, thereby enhancing team dynamics and efficiency

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

1. The Kanban Board Provides Transparency (Option A):

A Kanban board visualizes the flow of work, making it easy for the Scrum Team to see the status of work items, identify bottlenecks, and inspect and adapt their processes. This visual transparency is a fundamental aspect of both Scrum and Kanban and supports the empirical process control central to Scrum(

2. Kanban Helps Achieve Faster, Healthier Flow (Option D):

By focusing on optimizing flow (e.g., reducing Cycle Time and managing Work in Progress), Kanban helps Scrum Teams achieve a faster, more predictable flow of work. This improvement in flow brings more rapid transparency, allowing for more effective inspection and adaptation during Scrum events such as the Daily Scrum, Sprint Review, and Sprint Retrospective(

Option B (Kanban metrics are used in the Sprint Review to allow the Product Owner to inspect Throughput and adapt the Scrum Team's Cycle Time) is not necessarily accurate, as the Sprint Review focuses on the product increment and stakeholder feedback, not directly on Kanban metrics.

Option C (Kanban helps Scrum Teams deal with simple and complicated work where empiricism is not necessary) is incorrect because both Kanban and Scrum rely on empiricism (transparency, inspection, and adaptation) to deal with work complexity