Sprint Zero
Backlog Refinement Meeting
- Most product backlog items (PBIs) initially need refinement as they are too large and poorly understood.
- Large vague items are split and clarified considering both business and technical concerns.
- Backlog refinement meeting is also called as backlog grooming, backlog maintenance meeting or story time.
Sprint Planning Meeting
- At the beginning of every sprint, the product owner and scrum team hold a sprint planning meeting to negotiate which Product backlog items they want to convert into a working product during the sprint.
- The product owner is responsible to select items which are most important to the business.
- The development team is responsible for selecting the amount of work they think they can implement without accruing technical debt.
- By the end of the sprint planning meeting, we should answer two questions
- What will be delivered in the increment?
- How will the work be achieved?
- Sprint planning meeting is timeboxed to 4 hours for a 2 weeks sprint.
Daily Scrum Meeting
- Daily scrum meeting is timeboxed for 15 minutes.
- It is conducted at the same time, same place every day.
- All the team member answer to 3 questions
- What I accomplished yesterday?
- What will I accomplish today?
- What were the impediments I faced?
- If any topic required additional attention, it can be discussed in a sidebar meeting once everybody has answered these questions.
Sprint Review Meeting
- At the end of the sprint, the scrum team holds a sprint review meeting to demonstrate a working software to everyone who’s interested.
- The meeting should feature a live demonstration, not a report.
- After the demo, Product owner reviews the commitments made at the Sprint planning meeting and declares which item is
- Generally, timeboxed for 2-4hour for 2-4 weeks sprint.
Sprint Retrospective Meeting
- Each sprint ends with sprint retrospective meeting.
- Here team reflects on its own process, and inspect their behaviour to find any improvements that can be implemented into upcoming sprints.
- Scrum master should use a variety of technique to facilitate retrospectives like silent writing, safety check and happiness histogram.
- Often exposes organization impediments.