Currently we have three teams who start their two week sprint on Monday and end it on Friday. We have some team-members who have every Friday off. Planning sprint reviews on Thursdays or earlier is awkward, since the sprint is not yet done, or the whole Friday goes to "waste" on non functional tasks.
We want all the team members to be in the Sprint review and retrospective meetings and want to plan them at the end of the sprint. (We record Sprint review sessions for part-timers already)
Now we have figured out some possible solutions:
- Ask team-members to take another day off. (Asking the developers to re-arange their free day is no short-term option, mainly because of complex planning of child-care.)
- Start Monday with sprint reviews and retrospective meetings. Afterwards (after lunch) start the Sprint planning session and hope to finish on Monday. This leads to a very long "Talking" day and this might bore some and will feel ineffective.
- Start the sprint on Wednesday and end on Tuesday.
As we are evaluating option 3, my question is: Are there teams who have experience with mid-week start and end of sprints?
- What are the pro's and con's?
- Maybe we overlooked an option?
- Any other suggestions to handle and plan sprints around availability of part-timers is welcome.
Update Found a blog post which supports that this might be a good idea, should have googled first before asking this question maybe. Still interested in your experience though.
Update 2 We have been running sprints from Wednesday till Wednesday now for a couple of iterations. I have the feeling everyone is pretty happy with it. The teams asked to plan all the meetings on Wednesday, our day looks like this:
- 9:15 Setup meeting room and screen-cast recorders, dial-in external stakeholders
- 9:30 Start review sessions per team
- Start evaluation meeting after a short break.
- Start planning sessions
- 17:00 Have a beer and snacks :)