Waiting a day before starting new sprint?

[Thao Nguyen]

My team operates on 2 week sprints that start on Wednesday and end two Tuesdays later. My scrum master closes out a sprint at the end of day Tuesday but doesn't start the next sprint until end of day on Wednesday. Thus, there is a 24 hour time lag between the ending of a completed sprint and the beginning of the new sprint. I always thought that you should open up the next sprint without that kind of buffer, i.e. if he closes finished sprint end of Tuesday, he should open the next sprint at the beginning of the day Wednesday. What is the impact of leaving that 24 hour buffer in between sprints? Does it have any practical impact (development time, reporting, etc)? Is there a best practice?

[Jack Brickey · Accepted solution]

no real impact. you can always change the start date as well if you forget to start it. What I have traditionally done is to hold my sprint review and sprint kickoff in the same meeting. So I close the current sprint, discuss the next sprint and click start at the end of the meeting. That said, there are times we are ready to start, e.g. some tasks aren't scoped and the team needs a few hours to contemplate it. Depending on the exact situation your burndown might get skewed I expect.