Include the Sprint Goal in the Scrum Artifacts section
The Sprint Goal adheres to the definition of artifact (work or value to provide transparency and opportunities for inspection and adaptation.) Promoting it to artifact would make the guide tidier (presenting everything as a role/artifact/event,) facilitate the understanding and make it more difficult to forget it.
Jose Luis Soria
shared this idea
1 comment
Comments are closed-
Mark
commented
I disagree with David.
The Scrum Goal is inspected continuously: "As the Development Team works, it keeps the Sprint Goal in mind.... If the work turns out to be different than the Development Team expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint." (p10)
The Scrum Goal is also capable of adaptation: "A Sprint would be cancelled if the Sprint Goal becomes obsolete." (P8).
In many ways its inspectability and adaptability is no different from a Product Backlog Item which has been selected for a Sprint.
Finally, it is not a goal to which the stakeholders have to commit. It is crafted in the Sprint Planning and is not referred to in the Sprint Review. The only requirement is that it is a good summary of the objective and reason for a Sprint.
My preferred solution would be to add the Sprint Goal to the Sprint Backlog and change the name of the Sprint Backlog to differentiate it more from the Product Backlog.