Sprint Planning
Is it acceptable to add a sprint goal after the sprint planning meeting has taken place, but before the sprint review and retrospective? If so, under what circumstances? Thank you
Why would you need to add a Sprint Goal after the Sprint Planning was finished? Without a Sprint Goal, how can you carry out a Sprint Planning session?
Is it acceptable to add a sprint goal after the sprint planning meeting has taken place, but before the sprint review and retrospective? If so, under what circumstances? Thank you
From what you say, during Sprint Planning, the team will have failed to make their commitment. Why would that ever be "acceptable"? The whole point of a Sprint is to meet a Sprint Goal.
The project is multi faceted. In our last sprint planning session several goals were agreed for the current sprint. Another goal, which is urgent, has now been identified. It is this goal which we are considering adding into the current sprint too. Trust this makes sense?
Read the section of the Scrum Guide where the Sprint Backlog is described (https://scrumguides.org/scrum-guide.html#sprint-backlog) and the section that describes Sprint Planning (https://scrumguides.org/scrum-guide.html#sprint-planning) and see if you still have that question.
In our last sprint planning session several goals were agreed for the current sprint. Another goal, which is urgent, has now been identified. It is this goal which we are considering adding into the current sprint too. Trust this makes sense?
There is only supposed to be one Sprint Goal per Sprint, which guides the team in why they are carrying out the Sprint, provides focus, guides decision making, allows for some flexibility, and causes the Developers to unite and work as one team. As mentioned the Developers commit to one Sprint Goal per Sprint.
If a Sprint Goal becomes obsolete, the Product Owner may cancel the Sprint , and then a new Sprint starts and new Sprint Goal is defined.
A Scrum Master will need to step in and uphold Scrum by teaching the team about the Scrum Goal and help them understand the "why" behind the need for one Sprint Goal.
Scrum on
Thank you very much Chris.
I'm going to use a sports analogy. Consider Track and Field's 400 meter sprint. How many finish lines are there? One. That is because all of the sprinters are trying to achieve the same thing...cross the finish line first.
Now consider if there were 6 different finish lines? How would the sprinters know which line is the correct one to cross? And how would anyone know that the sprint is finished?
One goal helps to focus everyone on the most important thing.
Cannot agree more.. @Daniel.. well explained..