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.

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