The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. Sprint goals are the result of a negotiation between the Product Owner and the Development Team. Sprint Goals should be specific and measurable. While the selected work for the Sprint Backlog represents a forecast, the Development Team gives their commitment to achieving the Sprint Goal.
Sprint Goals should be specific and measurable I don’t mean SMART. Just prevent the goals become to vague. But some examples might be:
-
- Get feature X ready for release (hereby the Sprint Goal is delivering a feature)
- Check if the architecture enables the desired performance (hereby the Sprint Goal is addressing a risk)
- Test if users are willing to register before using the product features (hereby the Sprint Goal is testing an assumption)
An effective Sprint Goal…
-
- Serves to test assumptions, address risks or deliver features
- Ensures a focused Daily Scrum because the Development Team can use it to inspect their progress
- Provides guidance to the Development Team on why it is building the Increment
- Offers flexibility regarding the functionality implemented within the Sprint
- Helps setting priorities when “the going gets tough”
- Fosters teamwork and teambuilding by jointly working towards a shared Sprint Goal
- Supports the Product Owner in creating the product roadmap
- Stimulates Product Backlog cohesion when planning a release
- Can be used as an instrument for stakeholder management
- Supports a focused Sprint Planning by crafting a shared Sprint Goal
- Enables efficient decision-making