Posted date
Sprint Operation Guide
Table of contents
- Overview
- Basic rules and premise
- Sources
- Overall sprint planning
- Points of caution for contract development
- Sprint execution
- Prerequisites
- Sprint workflow
- Sprint planning meeting
- Daily work
- Product backlog refinement
- Sprint review
- Sprint retrospective
- Troubleshooting
- Stories are not finished within sprints
- A task was found to be missing from the story
- Product managers
- Role
- Story splitting cheat sheet
- Criteria for good stories: INVEST
- Story splitting format
- Daily scrums
- Sprint retrospective
- Introduction
- Workflow of retrospective
- Points of caution when conducting retrospectives
- Retrospective assessment sheet
- Source
- Criteria for good tasks: SMART
- Specific
- Measurable
- Achievable
- Relevant
- Time-boxed
Overview
This document describes sprint execution procedures to be carried out by the team working on system development.
Detailed procedures are described for scrum teams who are working on scrum development for the first time or are not used to the process.
Please use this guide to make improvements within your team based on factors such as the status of the project and the skills of the team members.
Basic rules and premise
The basic rules and premise of team operations are as follows.
Premise
- A scrum team consists of a product owner, scrum master and development team.
- For contract development, a product manager takes the place of a product owner.
- It is presumed that the development team has 7±2 members.
- It is recommended to carry out tasks in pairs.
- This is not to force teams to use pair programming but to ensure sufficient accuracy in quality checks and completion checks.
- However, pair programming is strongly recommended for the tasks that is difficult or implemented for the first time.
Operational procedures
- Create an overall plan.
- Carry out the project according to the procedures.
- Troubleshooting
Sources
- kawasima. Futsu No Jutaku Kaihatsu. 2015.
- Bill Wake. INVEST in Good Stories, and SMART Tasks. 2003.
- Derby, Esther and Larsen, Diana. Ajairu Retorosupekutibuzu: Tsuyoi Chimu O Sodateru “Furikaeri” No Tebiki, translated by Masanori Kado, Ohmsha, Ltd., 2007. (original title: Agile Retrospectives: Making Good Teams Great)
This document is provided under the international Creative Commons Attribution-ShareAlike 4.0 license.