Celebrating 10th Anniversary, Agile Conferences Pakistan 2024

Blog Article Detail

Sprint 0

Written by Sarfraz Aaron on Aug 29, 2022

Sprint 0 is not part of the Scrum Framework but more of a tool for the Scrum Master to initiate if needed depending on the scenario one finds themselves in. Let's use scenarios to illustrate the points.

Scenario #1

As a Scrum Master, when you are assigned to a new project and a new Scrum Team it may make sense to initiate Sprint 0 instead of kicking off Sprint 1 straight away.

In the beginning, the project scope is identified, the Scrum Team assigned and there are just too many questions that need to be addressed before anything is started, for example:

  1. Who is who and what is their role in the Scrum Team?
  2. What will be the format of planning, meetings, or even the schedules?
  3. Do we have anything to start Sprint Planning?
  4. Does anyone even know what is Agile, and Scrum, or even the purpose of each Scrum Event?
  5. Do we need an overview of the project components, work breakdown structure, or even a review of the project documentation, etc?
If these questions are not addressed from the get-go, then the Scrum Team's purpose, project goals, expectations, and project delivery becomes blurred; making it challenging for the Scrum Master to unite and grow the Scrum Team in Agile maturity and excellence.

Sample of activities to do

  1. Schedule a kick-off session with the below people and the aim is to allow all to introduce themselves and plan for the first 3 sprints (6 weeks of work) if possible: - Product Owner - Developers - QA - Technical Lead / Subject Matter Expert (SME) - Product Manager
  2. Submit a Request for a new Jira board, if not already done
  3. Schedule Scrum Events:
    • Daily Scrum
    • Backlog Refinement
    • Sprint Review
    • Sprint Retrospective
    • Sprint Planning
  4. Submit requests for the Scrum Team’s requirements, for example, software, installs, connectivity and access rights, etc.
  5. Add the issues into the Jira backlog following step #1
  6. For all tasks that are needed to be completed before Sprint 1 can start, add them to the Jira backlog as TASK issue type, including submission of requests
  7. Create Sprint 0 and add to it all the Jira issues from the backlog that are needed before Sprint 1 can start
  8. Sprint 0 start/end times can be 2 weeks or more, depending on the lead times for various activities to complete, for example, it may take 2 weeks for any Jira board creation requests, etc.
  9. Do a quick assessment of the Scrum Team’s knowledge of Scrum Framework and Agile Principles knowledge. If necessary, schedule some 1:1 or group sessions with the team to make sure all are on the same page when it comes to what is expected from the Scrum Team
  10. As Sprint 0 is active, start preparing for Sprint 1
  11. Must do Daily Scrums for Sprint 0 so that the Scrum Team can understand the format and the purpose of Daily Scrum
  12. There is no Sprint Review or Sprint Retro for Sprint 0

Scenario #2

However, if you’re assigned as a Scrum Master to an existing project, the Scrum Team is available and there is already a Jira board setup, then the below activities may be undertaken.

Sample of activities to do

  1. Schedule a kick-off session with the below people and the aim is to allow the Scrum Master to get to know the Scrum Team. Also to understand if Jira is set up properly, i.e. you may find that the Scrum Team is using the Jira Kanban board instead of a Jira Scrum board. As a Scrum Master, you will need to make sure you transition the Jira issues from the Kanban board to the Scrum board:
    • Product Owner
    • Developers
    • QA
    • Technical Lead / Subject Matter Expert (SME)
    • Product Manager
  2. Submit a Jira access request for the Scrum Master or if anyone else who needs it
  3. Review the Scrum Events to make sure the scheduled times are working for the Scrum Team
  4. Review the issues captured in the Jira backlog to make sure respective Epics and Versions exist for all issues
  5. Assess how the Sprints are scheduled, to make sure sufficient times are allocated
  6. Do a quick assessment of the Scrum Team’s knowledge of Scrum Framework and Agile Principles. If necessary, schedule some 1:1 or group sessions with the team to make sure all are on the same page when it comes to what is expected from the Scrum Team
  7. Make sure the Scrum Team attends all the Scrum Events and participates actively. It may be that only a handful of Scrum Team members speak and others keep quiet or they don’t get time to speak

Conclusion

Being assigned to an existing project and a Scrum Team makes it easy for the Scrum Master to get started quickly and evaluate and pivot where necessary.
As a general rule: "e; Do not come in and change everything"e; instead evaluate the situation, see how the Scrum Team is working, and then provide coaching where you see gaps.