Skip to main content

[VLOG] How To Create an Outcome Driven Sprint Goal

February 29, 2020

Hello awesome people. I am sorry I have been away for a while since I've been busy with stuff. Today's video is the continuation of my video: What Is The Definition of Done In Scrum | How Is It Different To Acceptance Criteria. Just like my previous video, many of my future videos will be referring back to this video.

Other than the Definition of Done, the Sprint Goal is the other most important aspect of Scrum. It is interesting to see that many Scrum Teams do not have any Sprint Goal, which makes their Sprint no different to a mini-waterfall. It is also interesting to see in the market that many people still think that the purpose of Sprint is to complete as many Sprint Backlog items as possible, which leads to a Sprint Goal that is output oriented and makes the team look like a feature factory. Often times I see many Scrum Teams spend a lot of time during Sprint Planning to figure out how they can fit in as many Sprint Backlog items as possible. 

Being output driven or a feature factory can make many Scrum Teams have no soul in their Sprint. Today's video is about how to come up with an outcome driven Sprint Goal. I hope today's video is helpful for your team, so they will be more inspired every Sprint. Please help us spread today's video, so that we can help more Scrum Teams to get out of the feature factory. I thank you for your continuous support.


What did you think about this post?