Question is -> should this all happen in one day (of course given the fact that it may be shorter - planning 1 hour, review 1 hour, retro 1,5 hour)?
The typical cadence of a the Scrum ceremony is to host Sprint Planning and then at the mid-point of the timebox run a Backlog Refinement ceremony. The Sprint Review occurs at the end of the timebox as that is when the work the team committed to delivering is due. Finally a Sprint retrospective takes place to discuss improvements in the working environment and practices prior to the next Sprint.
Traditionally for a two-week Sprint it would be
- Sprint Planning | 4 hours | First day of the Sprint
- Backlog Refinement | 2 Hours | Mid-Sprint
- Sprint Review | 2 hours | Last Day of the Sprint
- Sprint Retrospective | 1 hour | Last Day of the Sprint
I know some teams have experimented with Mon-Fri type Sprints, Wed-Wed Sprints but I have not come across a working practice which puts Sprint Review, Retrospective and then straight into Planning on the same day.
Personally, I feel that any benefits that arise from cramming all ceremonies into a single day would be eradicated by the severe drop in morale and concentration which would come from such a technique.
My firm answer is that Scrum ceremonies should occur across two days at the least but ideally a third day would incorporate backlog refinement.
My process as Scrum Master
I think that Sprint Planning is a fairly relaxed introduction to the new week and we plan on Mondays. I always ensure that I arrive with snacks and drinks for the team (cheese, doughnuts, gourmet coffee etc).
We start Sprint Planning approximately 1 hour after the working day begins which gives the team time to review emails after the weekend and collate all of their commitments and holidays and constraints before arriving at the planning session.
We actually run a three hour Sprint Planning session but that is an adaptation we found because of our workflow.
Normally it finishes around 12.15 at which point we break for lunch. In that break I place each of the committed cards back on the Board and the team return from lunch ready to start work by picking up their first cards around 1pm.
Our Sprint Planning Agenda is as follows (feel free to steal)
- 2 mins [SM] Open
- 5 mins [PO] Planning Vision and Roadmap
- 10 mins [Gov Mgr] Development and Architecture Status
- 5 mins [BP] Sprint Goal and Theme
- 5 mins [SM] Velocity Review
- 5 mins [SM] Sprint Timebox considerations
- 15 mins [All] Team Capacity
- 10 mins [All] Issues / Concerns
- 10 mins [PO] Review Definition of Done
- 2 hours [PO & Team] Product Backlog Items for consideration
- 15 mins [Dev Team] User Story Owners
- 15 mins [Dev Team] Assumptions / Dependencies for User Stories
- 5 mins [All] Agreement
- 15 mins [SM] Parked Items
- 5 mins [SM] Action Items
- 2 mins [SM] Closure
For Sprint retrosepctives we use a round robin of ideas from Retromat - a retrospective generator.