Sprint Backlog is NOT โ fixed during the Sprint.
Changes ๐๏ธ are allowed during the Sprint; work can be added โ or removed โ.
The Sprint Backlog represents the work that a Development Team needs to pull from the Product Backlog to achieve the Sprint Goal๐ฏ.
Although the Sprint Goal is fixed during the Sprint, the Sprint Backlog is NOT.
This would be unwise considering the core premise of Scrum: we can't create detailed plans for the future ๐ฎ.
Even if that future is a single Sprint, it is entirely possible that new insights or impediments emerge.
In short; a Sprint Backlog is flexible ๐คธ , as long as changes do not distract ๐ต ๐ซ from the focus on the Sprint Goal.
The Daily Scrum is an excellent opportunity to inspect ๐ต๏ธ and adapt and make adjustments to the Sprint Backlog.
The Sprint Backlog is a FORECAST ๐ฆ๏ธ by the Development Team about the functionality that will be part of the next Increment ๐ฆ.
Our goal should be to reach the desired outcome (the Sprint Goal) with the least amount of output (Sprint Backlog).
Embrace the emerging ๐๏ธ nature of the Sprint Backlog.
Encourage the Development Team to change, modify and improve the Sprint Backlog during the Sprint.
"The SPRINT goal is the defined destination ๐ฏ and the sprint backlog is possible ways ๐ฃ๏ธ to go there.
The paths can change to reach the same previously defined objective."
#scrum #sprintBacklog #canChange