Goal is defined as:
the end toward which effort is directed” or “the object of a person’s ambition or effort; an aim or desired result.
I don’t understand the debate over the Sprint Goal.
I also don’t understand how a teams can function and focus without goals (be they implicit or explicit although I would suggest that there is a danger in not making goals explicit).
If a team carves out a fixed set of time (a time-box) to do some work, they already have, albeit implicitly, established a goal i.e. completing a certain amount of work in a certain amount of time. I don’t consider this type of a goal to be a best goal we could come up with because it’s output focused and you know I favor outcomes over outputs. I will concede however, that this type of goal is probably better than no goal at all.
From the Scrum Guide, the Sprint Goal is:
an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.
Seems pretty straightforward to me with a lot of latitude for the Scrum team to create their goal. What do you think?
If your time-boxed work period has no goals, no aims, no objectives, no desired end what exactly is your team doing? Where are you headed?
(I’m pretty sure some folks reading this are thinking to themselves that time-boxing is an archaic practice and should be dropped altogether. Stay tuned for my next post).
And while this post has focused up till this point on teams working with time-boxes, I will go even further to suggest that any team that is developing and delivering software in support of a broader organizational vision – yes I’m looking at all the teams that say they are using Kanban out there – that doesn’t have time-bound (see Agile Manifesto Principle #3) goals is operating irresponsibly.
Goal are very useful. Use them wisely. Use them well.