LEARN. PRACTICE. GROW.Concept and mechanism
The Sprint Goal gives coherence to selected work and allows flexibility in how to achieve it. A Sprint Backlog is not an immutable contract for every initially forecast task. As Developers learn, they update the plan and can negotiate scope with the Product Owner without affecting the goal. Planning uses upcoming capacity, past performance, and the Definition of Done to form a forecast. Story points and velocity targets are not mandatory rules in the November 2020 Scrum Guide. The Scrum Master helps expose assumptions and prevents a forecast from becoming an unsupported promise about every item.
Guided application
In a fictional example, a team maintains a funds application while improving batch processing. An urgent incident reduces forecast capacity. The Scrum Master supports transparency about impact and a conversation between Developers and Product Owner about options, without ignoring the incident or unilaterally cancelling the Sprint. If the goal becomes obsolete, only the Product Owner has authority to cancel. If it remains relevant, the team adapts work while preserving quality and the goal. Use interruption data to improve the next forecast and discuss organizational conditions, rather than requiring overtime as an automatic response to variability.
A plan change can protect the goal; silently changing the goal hides the problem.
Common pitfalls
Forecast as an item contract; ignored incident; cancellation by Scrum Master; reduced quality to meet a count.
Related topics: Accountability and service to the team · Facilitation and useful events · Quality, flow, and impediments
Expose impact and facilitate adaptation by the accountable people.
Reference: The Scrum Guide · Scrum Guide November2020; Kanban Guide May2025; EBM May2024; primary guidance reviewed 2026-09-30