Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Scrum Basics: When Should We Schedule Sprint Transitions?

DZone's Guide to

Scrum Basics: When Should We Schedule Sprint Transitions?

· Agile Zone ·
Free Resource

Download the whitepaper on Product Centric Agile Delivery. Brought to you in partnership with Jile.

Originally written by Richard Lawrence at Agile For All.

We’re often asked which day or days are best for scheduling the Sprint Planning, Review, and Retrospective meetings.

In general, we prefer mid-week sprint transitions. People are most likely to take Monday or Friday off, so it’s easier to get the whole team reliably on Tuesday, Wednesday, or Thursday. Having a couple days to get started with the work for a new sprint and to build some momentum is nice, so I like planning on Wednesdays.

For a one week sprint, it’s possible to do Review, Retrospective, and Planning all on Wednesday morning. Or, you can do the Review and Retrospective in the morning, take a break to reenergize and to build the feedback from the previous meetings into your Product Backlog, and then plan in the early afternoon.

For a two or three week sprint, Review and Retrospective on Tuesday afternoon and Planning on Wednesday morning works well. With longer sprints, the meetings take proportionally longer; I find it useful to break them up across multiple days to maintain energy.

As with anything else in Scrum, you can make this an experiment. Make a hypothesis about what you expect to happen, try something for a while, and adapt if you’re not getting the results you like.

Download the whitepaper on Five dimensions of Scaling Agile in Large Enterprises. Brought to you in partnership with Jile.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}