Loading...
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
Daily scrums
Participants: Members of the development team
Duration: 15 minutes
- Greet each other.
- Report on progress in tasks assigned at the previous scrum.
- Confirm whether any stories can be closed and then close them.
- Decide on pairs.
- A group of 3 is possible if there is an odd number of team members.
- Assign tasks to pairs.
- Assign 5 hours of work to pairs and 7.5 hours of work to any groups of 3.
- Retrospective of the Try that is added to the project wiki for sprint.
- If there are any amended tickets, confirm the number of items with the programmers responsible for those tickets.
- Confirm the following points in the list of risks/list of issues.
- Schedule
- Progress
- Whether there are any risks that will cause issues
- Judge whether escalation is needed in the progress.
- Yellow signal: 50% of the way through the sprint period
- Red signal: 80% of the way through the sprint period
- Confirm whether there are any events.
- Confirm whether there are any other points that need to be communicated.
- Finish with some words of encouragement to each other.
