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
Product managers
Role
The role of product owner has the role of product manager plus an extra. Contract development does not have a role that is analogous to the stereotypical product owner, so for the purposes of contract development, we have used the term “product manager”.
When iterative development is done within discrete phases, a safety lead is needed, so in most cases, the need to implement stories needs to be assessed before agreeing on any points with the client during scheduling. It is the product manager’s responsibility to find hotspots and ensure that the team carries out design work according to the general OCP rules to ensure that anything created before this point is not wasted.
