- External reference:
Only the developers have the liberty to decide how they will fulfil that commitment2. Yet, they remain transparent and they negotiate possible change of work during the sprint, even though the sprint goal remains unchanged3.
The fact there is one and only one goal make the team work together toward this goal.4
Notes linking here
- are story points compatible with scrum
- being committed towards the sprint goal does not necessarily mean always working towards it
- being committed vs spending all one’s time
- commitment (scrum)
- critiquer sans solution, ça peut quand même aider
- dailies are not about telling our live
- daily scrum
- débat sémantique
- finding a Sprint Goal to a diverse team
- focus (scrum)
- inability to use Sprint Goals is symptomatic of serious Product Management problems
- method is a tool, not a toolbox
- misconception about the daily meeting
- métaphore salade vs pâtes
- natural software development using #NoEstimates and variable length sprints
- product goal (scrum)
- product owner does not define the sprint goal the whole scrum team does
- scrum artifacts
- scrum events
- scrum team
- sprint backlog
- sprint planning
- what if the scrum team fulfills the sprint goal before the end of the sprint?
If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal.
Sprint Goal also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives.