Concept of "The Sprint"
Questionable in the ScrumGuide.
I am not sure when Jeff & Ken decided "The Sprint" would include all meetings. Maybe when you decided sprints (iterations) should run back to back? Remember those discussions and my first sprints as a Scrum Master had gaps between sprints where we would work on the Product Backlog and get PBI's "Ready".
However, when I hear your talks, read articles, read the ScrumGuide, there is plenty of hints that the Sprint is after sprint planning and before sprint review.
Sprint planning: As the words say you plan the work for the sprint. How can you plan something you are doing? I feel confident the real meaning when you invented the the expression was for you describe what the team would do after sprint planning.
Sprint review: Same thing here and as the expression say you review the work the development team have done (not sprint planning which is part of the sprint). Again the expression most likely goes back to the old definition of the Sprint.
Sprintbacklog: Includes the work of the sprint, so it should include sprint planning, sprint review and retrospective? Again expression come from the old definition of the Sprint.
Expressions in the Scrumguide
Cancelling a Sprint
When a Sprint is cancelled, any completed and “Done” Product Backlog items are reviewed. I guess the Sprint is not yet cancelled as we still do a sprint review (and possibly retrospective)?
Sprint cancellations consume resources, since everyone has to regroup in another Sprint Planning to start another Sprint. Here it clearly says that sprint planning is not part of the sprint.
The work to be performed in the Sprint is planned at the Sprint Planning. So sprint planning is not work?
Is it the goal of the "development work" or the Sprint (including all meetings)?
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. So the sprint backlog is not a backlog of the the sprint but of "development work"?
The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved; I assume you mean during part of the sprint, "Heart of Scrum".
There are many examples but just to show where we are
On the Scrum Inc website
The Sprint Backlog is an ordered list of Product Backlog Items, preferably User Stories, that the Team believes it can complete during the coming Sprint.
How can it be the coming sprint when we are in the Sprint?
Some questions from the open assessment on scrum.org
Who is responsible for managing the progress of work during a Sprint?
The Product Owner
The Scrum Master
The most junior member of the Team
The Development Team
Correct answer is development team. Is sprint planning and sprint review progress of work? If so I would say PO and Development Team.
Which statement best describes the Sprint Review?
It is a demo at the end of the Sprint for everyone in the organization to check on the work done.
It is a mechanism to control the Development Team's activities during a Sprint.
It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.
Correct answer is the last one. I would say the outcome of the sprint is the potential releasable increment, which is yet not accepted untll after sprint review. Correct answer hints Sprint is the development work during the Sprint.
When does the next Sprint begin?
When the Product Owner is ready.
Immediately following the next Sprint Planning.
Immediately after the conclusion of the previous Sprint.
Here it is fully correct and not dubious :))
Anyway, I believe there is something irrational about calling it Sprint Planning and sprint review when it is part of the Sprint. How can you plan and/or review something you are in?
My suggestion would be to (think I have said it before) go back to the old definition of the Sprint and write it like this
Iterations run back to back.
An Iteration consist of Sprint Planning, Sprint, Sprint Review and Retrospective.
2 commentsComments are closed
Pierre Mengal commented
Mark, this is because they are static flow diagrams. It's obvious that the Spring Backlog content is being processed by the Sprint. So see those as inputs in the sprint (which is the circular drawing).
I'm sure that you will prefer this one: https://labs.openviewpartners.com/wp-content/uploads/files/2013/05/Scrum-Sprint_sized.jpg
I agree that people find this confusing.
As a new user I was looking for visual representations to help me learn the concepts. If you look for visual representations of Scrum they (nearly) all have the Sprint Backlog being created outside the Sprint. Not only does this not represent the current description of Scrum, it also makes a nonsense of the circular metaphor which shows that each Sprint follows directly after the previous one.
However, as someone learning Scrum for the first time I think that including everything in the Sprint time-box is important. The downside of taking the non-development work outside the Sprint is that the time-box for the Sprint disappears. You need the stakeholders to know that their interaction with the done product in the Sprint Review has to be done within the timebox, as does the planning and retrospective.
I agree that everything that the Scrum Master and Product Owner does is also work. To solve your issue the word "work" should perhaps be replaced by "development (work)" (or some other more specific term) when it refers to the development work as described on page 8.