Konubinix' opinionated web of thoughts

Sprint Goal

Fleeting

  • External reference:

During the sprint planning, the developers commit toward a sprint goal and only a sprint goal.1

It is similar to the notion of projet (first horizon of commitment) in gtd, while product goal is more like gtd goal and gtd vision.

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

  1. The Sprint Goal is the single objective for the Sprint

    — https://scrumguides.org/scrum-guide.html

     ↩︎

  2. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it.

    — https://scrumguides.org/scrum-guide.html

     ↩︎

  3. 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.

    — https://scrumguides.org/scrum-guide.html

     ↩︎

  4. Sprint Goal also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives.

    — https://scrumguides.org/scrum-guide.html

    Developers work during the Sprint, they keep the Sprint Goal in mind

    — https://scrumguides.org/scrum-guide.html

     ↩︎