Scrum doesn’t inherently prescribe any set day to start a sprint. This begs the question if the topic bears any merit. And if yes, then what might be the best suitable day to start a sprint? We believe this is a topic of some importance, and will try to make my point through the next few paragraphs. Let’s take a two week sprint scenario as an example for the purpose of this exercise.
Teams consider Mondays best to start sprints, being the first day of the week. A point we don’t quite agree with. Let us look at this scenario starting backwards. Sprints planned this way end up on a Friday or “fun day”- prone to being lean on account of long weekends or planned holidays. This invariably leads to diluting the ‘sprint end day’ activities through poor participation. A situation far from ideal, given that the last day of a sprint is when the sprint is reviewed, and team achievements are showcased to a wider audience.
Here are a few points why Monday or Tuesday of the week may not be ideal days to start a sprint .
- Monday : people are usually in a weekend hangover mode and could experience Monday blues leading to lower energy levels or less focussed sprint planning. Starting sprint planning may be difficult as many are usually busy finishing the leftovers from Friday thereby sprint planning could be less productive.
- Monday or Tuesday : If a sprint starts on these days it must end on a Thursday or a Friday which again lands us in the same spot as mentioned in the previous paragraph.
After evaluating the reasons why Monday or Tuesday are not ideal it leaves us with Wednesday Thursday. Midweek is always more productive as the team is in the zone of finishing the work . Also Mon and Tues are enough to tie the loose ends and to get started with a new sprint on Wednesday or Thursday.
The reason why Friday is not an ideal option to start a sprint is simply that the upcoming weekend that follows Friday makes it difficult for the team to pick from where they left and getting the right momentum is generally difficult.
“Unlock the potential of your business with agile consulting services. Customized solutions to drive growth and adaptability. Explore our offerings now.”
In Contrast
Let us also contradict ourselves, when we finish the sprint on Friday then a team member has a relaxed weekend with no thoughts lingering around and they are ready for a fresh start on Monday 🙂
If you start a sprint over mid-week, say Wednesday, then it might happen that the team mates who are feeling pressure of lagging behind may use the weekend as an opportunity to finish the work. It causes a work-life imbalance and that may end up making the team more stressful.
To mitigate this, the Scrum Master’s role is crucial to protect team members in setting right expectations, plan their work effectively and also be conscious to finish it within the working days.
To Summarize all the above points, it is best to start a sprint on Wednesday or Thursday and end it on Tuesday or Wednesday, so as to keep the energy levels high and maximize throughput using focus time.
Additionally, in our experience we have seen some really bad practices wrt starting and ending a sprint. We have composed a few pointers which must be avoided while sprinting.
5 Things To Avoid While Sprinting
- Dont cancel or stop the sprint midway unless the sprint goal becomes meaningless as the business has changed its direction
- Don’t change the duration of the sprint based on the work intake of the team. Here capacity planning during the sprint planning event is the key. Also, we should learn to split the work-items into small valuable items to avoid spill-overs.
- When is sprint finished? Don’t advance the end date to accommodate holidays on the first & last day of the sprint, instead reduce the capacity of the sprint. As it will keep the rhythm intact. For holidays falling in between the sprint, adjusting the capacity is the key.
- Don’t extend the sprint if the work has not been completed. Such practices take away the core of scrum framework where the idea is to incrementally deliver outcomes in fixed iterations as it leads to habit formation and create a fat-free environment for the development to be more productive. The worst that could happen is spill-over to the next sprint and that’s OK as we will retrospect and try to improvise in our next sprint.
- Don’t shorten the sprint if the work items have been completed earlier than planned. In such a scenario, you may pull the work from the backlog and start working on it.
Teams should think on the reasons shared for preferring a Wed/Thur as the start of the sprint. And, if the other cadence works well for your team, then please go-ahead with that. The whole point of sprinting is to fail faster by shortening the feedback loop and creating valuable outcomes incrementally.
How To Start A Sprint?
Here’s a step-by-step guide to help you start a sprint:
Step 1: The team, product owner and stakeholders gather for a planning meeting. This event is pre-booked for a couple of sprints ahead of time. As it is a routine event hence no one should need a reminder.
Step 2: Together we all review Goals and Objectives so as to align the team with purpose
Step 3: Collaborate to define the sprint’s specific goals, ensuring they’re achievable and aligned with the project’s objectives.
Step 4: Choose user stories or tasks from the product backlog that support the sprint goals. It is actually presented by the product owner based on order of priority and also the next logical increment that could add value to the ongoing product.
Step 5: Team estimates the effort required to complete each user story or task in alignment with the capacity that they have within the sprint. Here we may end up either under-estimating or overestimating but this team learns as they spend some time sprinting & retrospecting.
Step 6: Team members based on their expertise and capacity pull us the work & decide who will do what so as to fulfill the goals of the sprint.
Step 7: Ensuring adherence to ‘Definition of Done’
Step 8: Vet the sprint backlog once again based on goals defined and capacity. Ensure it also incorporates the feedback from the previous sprint review, learnings from retrospective, the technical advancement for system stability etc.
Step 9: Start the Sprint in your tool (JIRA, ADO etc) and have the team start working on their assigned tasks.
How To Conclude A Sprint?
Let’s discuss how to close a sprint. On the last day of the sprint, we have 2 essential events, Sprint Review & Sprint Retrospective. Both help us in inspecting the experience of the sprint and adapt the feedback or areas of improvement. Following is a step-by-step guide of your last sprint day events:
Step 1: Sprint Review event is pre-booked, here team demonstrates and reviews the work completed during the sprint.
Step 2: Team showcases the work to stakeholders and team members, and gathers feedback.
Step 3: Ensure to collate all the feedback and share it back with reviewers and also Product Owner ensures to vet it, discuss within team and then populate the backlog accordingly
Step 4: Then, conduct Sprint Retrospective and here we check within team,
- What went well
- What didn’t go well
- Lessons learned
- Improvements for the next sprint
Step 5: Then, ensure all tasks are completed in your PM tool, and the sprint backlog is updated before closing the sprint
Step 6: Document the sprint’s progress, successes, and challenges for your note keeping to reference
Do let us know if you think there are other considerations which are important in your environment. Please reach out to us at “consult@benzne.com” for any feedback, suggestions, questions or support from Benzne Agile Transformation services in designing and implementing agile ways of working at your organization.
Frequently Asked Questions About Sprint Start and End Day
- What is the best day to start a sprint, and why?
Below options are the best day to start a sprint as per our experience as an agile transformation service and agile consulting company.
- Wednesday. Beginning a sprint on Wednesday offers:
- A mid-week reset, helping teams regain focus and momentum
- Avoidance of Monday meetings, allowing for a head start on work
- A consistent schedule, avoiding conflicts with weekend or Monday
- Monday. If you want to aligns with the traditional work week, allowing teams to:
- To avoid weekend working
- Aligning with org-wide cadence of starting work on Mondays
2.How to effectively close a JIRA sprint?
How to close a JIRA Sprint? The sprint in JIRA should be closed after the following checks:
- Sprint review & retrospective has happened
- All the tickets are updated to right status (Epics, Stories, Tasks, Sub-tasks) i.e. the completed are in DONE state and those which are not we know that would be carry forwarded to next sprint or will go back to backlog
- If you are tracking time then all team members have logged it
- Check the burndown chart is up to date
- Now, I think we are in good shape to close the sprint
3.Why do some teams prefer starting sprints on a Wednesday?
Why do sprints start on Wednesday for some teams?
- A mid-week reset, helping teams regain focus and momentum
- Avoidance of Monday meetings, allowing for a head start on work
- A consistent schedule, avoiding conflicts with weekend or Monday
4.Should you extend sprints if tasks are not completed by the end?
No. The undone work will be reviewed and the Product Owner along with the team decide to plan it either moving to the next sprint or may be later if it has been untouched. When is a sprint over – The sprint end is pre-defined and we should follow the rhythm and learn to plan, estimate, and implement effectively.
