How to Craft A Good Scrum Sprint Goal

Scrum is a goal driven framework rather than scope driven or velocity driven framework. However, many teams who are using Scrum does not have any Sprint goal. Without a Sprint Goal, a Sprint is no different than a mini-waterfall. Crafting a good Sprint goal is not easy. A good Sprint goal creates focus and synergy within the Scrum team. This video will explain some tip I have used to craft a good Sprint goal.

[scrummasterinblack]

If Scrum Guide is summarised into one sentence, it would be a framework for delivering an increment that meets Sprint Goal. Yet many teams are struggling to come up with a good Sprint Goal. I like asking questions. This video provide the questions I ask Product Owner so that they can come up with a good Sprint Goal.

[marleenkluyver]

Great way to emphasise the key points in your video by highlighting them!!!!

The purpose of a Sprint is to achieve business outcome.
One Goal, One Purpose, One Direction

A Good Goal should be outcome driven
A Good Goal should be measurable
A Good Goal is specific and attainable in one Sprint

Q1. If this is going to be your last Sprint what makes it important that makes you still want to fund this Sprint?
Q2. How will customer behaviour change after we deliver the increment?
Q3. What business metrics will be impacted and by what percentage, after we deliver the increment from this Sprint

[ClaudioRossi-zznp]

Amazing video Jousha, as always! I liked a lot the analogy you made with the Tower and the powerful questions for POs. 1:47 I think you still had some fresh remembers about a nice Pizza ;-)

[mustofin]

3 mantra powerful question untuk memancing PO membuat Goal yang

[SeliaSu]

I love your videos, thank you so much for sharing all this knowledge in such a clear way! One question: how do you go about outcome based sprints when working on a project and just starting the work? I.e. a project that delivers a new way for customers to access data in a single point. The final outcomes of the project are there, but the beginning of the project would be to set up the technology that'll host the data, migrating that data etc. One or more of the first sprints would focus on building that database and migrating the data there. How do you make those sprints outcome based, when they're actually "only" delivering part of a bigger outcome that won't be realized until various sprints after?