YDS: How to Write a Good Sprint Goal in Scrum

Join this channel to get access to the perks and exclusive videos:

The video discusses how to write a good Sprint goal in Scrum. Ryan and Todd suggest avoiding the use of "and," "or," commas, and ticket numbers in Sprint goals. They also address whether it's fine to have Product Backlog Items (PBIs) that are not directly related to the Sprint goal, and conclude that it is acceptable as long as the work tied to the Sprint goal is given priority.

Leave us a comment and let us know what you think!

Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems.

For more information about Agile for Humans, visit:

#facilitation #facilitationskills #ScrumMaster #ScrumMasterTraining #Scrum #ScrumFramework #HowToBecomeAScrumMaster #ScrumMasterCertification #AgileForHumans #FreeScrumMasterCourse #FreeScrumTraining

[fenrisomen]

The title of this one was very interesting to me. But the answer of "a 3 week sprint is long try a shorter one" is not one that's particularly helpful to me.
I've worked with small and large teams and with 2 and 3 week sprints. Bigger teams and longer sprints do in my experience make setting good goals harder. So questions like can we split in two smaller teams (and still retain the skills in each team individually to bring stuff to done) or can we shorten the sprint are valid questions.

But in the domain of robotics where i work and the quality and safety requirements we have for done 2 weeks is to short for most products. So I'd love to see another video on this with some other tips about this topic.

[ashleydickson]

Video get cut off? Did answer how to write a sprint goal with an example