Return to site

Scrum from the Trenches - the Sprint Goal ๐ŸŽฏ by Jasper Alblasog Post Title

ยท scrum

The Sprint Goal

The most recent version of the Scrum Guide (2020) ๐Ÿ†• talks about the Product Goal as a commitment to the Product Backlog

and the Sprint Goal ๐ŸŽฏ as being the commitment for the Sprint Backlog.

The Sprint Goal is crafted during the Sprint Planning.

It helps bring focus to the Sprint.

During the Daily Scrum, the Sprint Goal should be the main topic of conversation.

๐—–๐—ต๐—ฎ๐—น๐—น๐—ฒ๐—ป๐—ด๐—ฒ๐˜€ ๐˜„๐—ถ๐˜๐—ต ๐˜๐—ต๐—ฒ ๐—ฆ๐—ฝ๐—ฟ๐—ถ๐—ป๐˜ ๐—š๐—ผ๐—ฎ๐—น

๐‘ช๐’‰๐’‚๐’๐’๐’†๐’๐’ˆ๐’† #1: ๐‘ป๐’‰๐’†๐’“๐’† ๐’Š๐’” ๐’๐’ ๐‘บ๐’‘๐’“๐’Š๐’๐’• ๐‘ฎ๐’๐’‚๐’

Not having a Sprint Goal might not block ๐Ÿ™… ๐Ÿ›‘ you from delivering a releasable increment.

However, a lot is gained ๐Ÿ˜‰ when teams focus on the Goal of the Sprint.

What's the reason there is no Sprint Goal? Mostly there also is a lack of focus.

Ask the Product Owner what is it that we want to achieve at the end of this Sprint.

๐‘ช๐’‰๐’‚๐’๐’๐’†๐’๐’ˆ๐’† #2: ๐‘ป๐’‰๐’† ๐’˜๐’๐’“๐’Œ ๐’Š๐’” ๐’•๐’‰๐’† ๐‘บ๐’‘๐’“๐’Š๐’๐’• ๐‘ฎ๐’๐’‚๐’ ๐Ÿ“ƒ

Avoid Sprint Goals like:

"Get Jira tickets 17322, 17323, 171400, and 17888 done". ๐Ÿคฆ


to sum up, all the selected Product Backlog Items are squeezed into a sentence.

Product Backlog Items in the Sprint are the outcome ๐Ÿ“ฆ, and the Sprint Goal should be leading it ๐Ÿ”.

The Product Owner should not โŒ try to keep all the stakeholders happy by giving them all a breadcrumb.

The stakeholders should be managed โœ… and the Product Backlog should be organized around features that deliver value for customers at the end of the Sprint.

๐‘ช๐’‰๐’‚๐’๐’๐’†๐’๐’ˆ๐’† #3: ๐‘ป๐’‰๐’†๐’“๐’† ๐’Š๐’” ๐’๐’ ๐’“๐’๐’๐’Ž ๐’‡๐’๐’“ ๐’‚๐’๐’š๐’•๐’‰๐’Š๐’๐’ˆ ๐’†๐’๐’”๐’† ๐Ÿคฏ

We have a Sprint Goal! ๐Ÿ‘

But there is no room for anything else. ๐Ÿ˜ญ

What if:

* The solution thought of turns out to be a lot harder to implement;

* Production failures need fixing;

* Danny (the guy everyone relies on) is ill (again!) ๐Ÿค’;

* The Product Owner promised ๐Ÿคฉ a particular stakeholder that he can get this last-minute fix in the Sprint anyway.

* ... and so on ...

Having a full Sprint means imminent risk โšก in achieving the Sprint Goal!

Choose your focus point for this Sprint. And make that your Sprint Goal.

Use a primary and secondary goal in a Sprint, so that the focus remains on the main goal, but there is still cohesion on the rest of the Sprint.

๐‘ช๐’‰๐’‚๐’๐’๐’†๐’๐’ˆ๐’† #4: ๐‘ป๐’‰๐’†๐’“๐’† ๐’Š๐’” ๐’๐’ ๐’‡๐’๐’„๐’–๐’” ๐’๐’ ๐’•๐’‰๐’† ๐‘บ๐’‘๐’“๐’Š๐’๐’• ๐‘ฎ๐’๐’‚๐’ โŒ๐Ÿ”Ž

You have a good Sprint goal but you do not use it, leaving it behind.

Make sure the Sprint Goal is visible somewhere for everyone to see. ๐Ÿšจ

Talk about it (during Daily Scrum)! ๐Ÿ—ฃ๏ธ

Make sure Product Backlog Items on your Sprint relevant to the Sprint goal are on top and worked on first: colorize ๐ŸŽจ or tag them!

๐‘ช๐’‰๐’‚๐’๐’๐’†๐’๐’ˆ๐’† #5: ๐‘ป๐’‰๐’† ๐’ˆ๐’๐’‚๐’ ๐’Š๐’” ๐’๐’๐’• ๐’‚ ๐’ˆ๐’๐’‚๐’ ๐Ÿ˜ต ๐Ÿ’ซ

It's important that the Sprint Goal has a -what- focus: what do we want to achieve?

"Change the page to support HTML5 elements"

... is probably not the best Sprint Goal to work on.

#scrum #sprint #goal