- Have a team name. An identity for the team goes a long way.
- Identify all Scrum team members, role, skillsets, contact information and working hours. Especially useful for distributed team
- Conference number and participant code (usually for distributed team)
- Taskboard URL (if not using a physical board)
- Source code URL and access
- Working Agreements (at least 3 not more than 7)
- Team Values (at least 3 not more than 7)
- Availability of Product owner. Identify slot of time where PO is or not available.
- Will the PO attend the daily standup meeting?
- What should the team do if the PO is not available for sprint planning, review, question or extend period of time (vacation, sick leave etc)
- Sprint length
- Sprint start date
- Sprint Planning (day/time/location)
- Daily standup meeting (time/location)
- Sprint review (day/time/location)
- List of important stakeholder to be invited for sprint review
- Sprint retrospective (day/time/location)
- Backlog grooming/refinement (day/time/location)
- Identify important milestones for the project
- Definition of Done
- Definition of Ready
- Story point baseline
- Estimation scale (Fibonacci or power of 2 or etc)
The above activities can be considered as part of sprint zero. It should not be taking more than 2 days if the relevant parties are available. Once the above activities are completed, it is time for the Scrum Master and the Product Owner to prepare the prioritized backlog and have a product grooming session with the team before the actual sprint begin.
- Sprint zero should also cover the technical setup of the necessary tools and environment
- You might also want to include a half day Scrum training for the team if the team is new to Scrum