When Developers reserve capacity for unplanned work during a Sprint, the Sprint Goal becomes even more crucial. It serves as the guiding objective that aligns the team's focus amidst uncertainties or when unplanned work is introduced. By having a clear Sprint Goal, the Developers can ensure that any new items brought into the Sprint Backlog still align with the overarching objective of the Sprint, helping them maintain focus and coherence in their efforts throughout the Sprint

When a Scrum Team uses Kanban, they can visualize:
*The Product Backlog: By making the Product Backlog visible, the team can track what work items are upcoming and prioritize them effectively.
*The Sprint Backlog: Visualizing the Sprint Backlog helps the team see the work planned for the current Sprint, track progress, and manage flow.
*The Definition of Done: Making the Definition of Done visible ensures that all team members and stakeholders understand the criteria that must be met for work to be considered complete

adaptation loop.
Explanation:
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