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

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