Scrum balances flexibility with Sprint-level stability. Once the team commits to Sprint work, outside interference and arbitrary requirement changes should be prevented so that the Scrum Team can maintain focus and produce the committed increment.

The Scrum Master helps protect the Scrum Team from disruption, while the Scrum Team maintains commitment to the Sprint work. New Change Requests generally enter the Prioritized Product Backlog and are evaluated and prioritized for a future Sprint rather than being inserted indiscriminately into the active Sprint.

Option B violates this stability principle by suggesting that a Sponsor should introduce and approve changes directly during the Sprint. Option C is incorrect because Scrum does not seek “complete stability” across the project; the overall project remains deliberately adaptive. Option D is too absolute. Change approval authority can vary according to organizational tolerances and program/portfolio governance, even though the Product Owner controls project backlog prioritization.

Scrum's objective is therefore stable execution inside the Sprint and flexibility between Sprints, not resistance to change throughout the project.

Study Guide reference: Change - > Balancing Flexibility and Stability; Maintaining Sprint Stability.

========