“After the Sprint Review and prior to the next Sprint Planning meeting, the Scrum Team has a Sprint Retrospective meeting.” (scrum.org, The Scrum Guide, page 14).
This sounds completely sensible. So people all around the globe conduct these meetings in this order.
It does not have to be that way!
In our team we have 2-week iterations. So the standard meetings can be held all on the same day: Review in the morning followed by Retrospective and finally closed by Planning in the afternoon. We did that for a few iterations. Our last meeting day was hit by a railway strike. One team member could not come. She is working off-site and definitely wanted to attend the retrospective. She said conducting the review and planning without her is ok. We left out the retrospective and moved it by a week.
The effect was marvelous! We experienced a very focused retrospective. Observations:
- People were less tired
- No distraction by the product; people did not get distracted by features or bugs
- Review and planning were completely focused on the product
- If required, meeting schedules can easily be extended ad hoc
I think we will do this more often. Having two days of meetings of course has the drawback that off-site team members need to travel twice. Nonetheless, for us it worked great and the results outweighed this annoyance by far!