Project with several sprints
Hello Everybody,
I read the Scrum Guide several times but was unable to find the answer I'm looking for:
Scrum Guide mentions that the Spring goal must be defined during the Spring Planning --> OK
On the other hand, it is clearly explain that the Sprint N+1 starts immediately after the end of Sprint N --> OK
--> My understanding is that the sprint goal is the final goal of the Sprint, contrary to product goal which is the final project goal.
How can we define a goal for each sprint if we cannot do a Sprint planning for each one of them ?
Thanks guys in advance !
You can do a Sprint Planning for each Sprint:
Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team.
When Sprint N ends, the team holds a Sprint Review with key stakeholders. At this Sprint Review, the team and the stakeholders look at the team's performance in Sprint N, such as if the Sprint Goal was accomplished and how the work that was Done delivers value. The team and stakeholders also discuss changes in the environment and how those changes impact the Product Goal and the Product Backlog, revising as necessary.
Sprint N+1 begins with a Sprint Planning, where they consider the (potentially) revised Product Goal and Product Backlog, along with past performance, to determine a reasonable Sprint Goal for the upcoming Sprint.
How can we define a goal for each sprint if we cannot do a Sprint planning for each one of them ?
The Sprint is a container for each of the other four events, including Sprint Planning. So Sprint Planning happens in every Sprint every time.
Sprint Planning is not something that happens outside of or between Sprints.
How can we define a goal for each sprint if we cannot do a Sprint planning for each one of them ?
Sprint planning happens every sprint and that is where the team agrees on the sprint goals.
Here's another thought. An unordered Product Backlog is often the cause of teams that struggle to craft a Sprint Goal in Sprint Planning. The Product Owner can play a part in this before the Sprint starts if the organization has empowered them. Often a Product Owner can order the Product Backlog through Product Backlog refinement preferably before the Sprint, either by his/herself or with the Scrum Team. Ordering by a cohesive set of Product Backlog items (PBIs) is key and can bring order to a chaotic Sprint Planning.
In Sprint Planning the Product Owner proposes an objective and outcome of value he or she would like to see. That's topic 1: Why is this Sprint valuable?
The PO's objective and ordered Product Backlog often makes it easier for the Scrum Team to craft the Sprint Goal in Sprint Planning.
If they get stuck and can't choose, the Scrum Team can ask the Product Owner what he/she views as the one most important objective for the Sprint to get us one step closer to the Product Goal and go with that as their North Star. Not every PBI has to align with the Sprint Goal.
All of the advice above is what I would have said if I had gotten here earlier. :)
But one thing I want to add. Your topic is titled
Project with several sprints
The following statement is from the Scrum Guide's section that explains the Sprint. I added the emphasis.
Sprints enable predictability by ensuring inspection and adaptation of progress toward a Product Goal at least every calendar month. When a Sprint’s horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase. Shorter Sprints can be employed to generate more learning cycles and limit risk of cost and effort to a smaller time frame. Each Sprint may be considered a short project.
In my experience, the Scrum framework is best used when supporting products that are long lived. The Product Backlog contains all of the work needed to enhance and support the product during it's life. While you may internally view a body of work to add some enhancements as a project, to the Scrum framework, it is just a set of work that is iterated upon to deliver usable increments of value to the stakeholders. So, it is likely that most anything you view as a project is going to spread across multiple sprints. And each Sprint will deliver at least one usable increment of value to the stakeholders while allowing the stakeholders to give feedback that can help the Scrum Team make any adjustments needed as the work is being done.
Imagine Sprints as a train track that goes around in a circle. Each Event is like an Inspect and Adapt station along this circular track. First stop, Sprint Planning, followed by Daily Scrum, Daily Scrum, (how ever many Daily Scrums you have based on your Sprint duration), Sprint Review, Retrospective and back to Sprint Planning with another rotation around the Events track. With each trip around the Sprint track you are setting a Sprint Goal at Sprint Planning. Does this help? All aboard?