# Scrum meeting agenda: sprint planning

**Sprint:**   
**Date:**   
**Time:** At most 8 hours for a one-month sprint, usually shorter  
**Facilitator:** Scrum master  
**Attendees:** Product owner, developers, scrum master  

| Item | Owner | Time | What we need to leave with |
| --- | --- | --- | --- |
| Last sprint result and carry-over | Scrum master | 10 min | Carry-over items back in the product backlog, re-ranked |
| Capacity for this sprint | Developers | 10 min | Agreed person-days available |
| Why: proposed sprint goal | Product owner, then the whole scrum team | 15 min | A sprint goal the whole team agrees on |
| What: select backlog items | Developers with the product owner | 40 min | Items pulled in, each estimated and clear enough to start |
| How: plan the delivery, first items in detail | Developers | 30 min | A plan the developers own, with work for the first days broken down |
| Confirm goal, risks and read-back | Scrum master | 10 min | Final sprint goal, each risk with an owner |

## The other scrum events

| Event | When | Timebox (Scrum Guide, for a one-month sprint) | What it produces |
| --- | --- | --- | --- |
| Daily scrum | Every working day, same time and place | 15 minutes, whatever the sprint length | A plan for the next day, blockers raised |
| Sprint review | End of the sprint | At most 4 hours, usually shorter for shorter sprints | Feedback from stakeholders, an updated product backlog |
| Sprint retrospective | After the review, before the next planning | At most 3 hours, usually shorter for shorter sprints | One or two improvements for the next sprint |
| Backlog refinement | Ongoing, often one session mid-sprint | No set length (an activity, not a scrum event) | Items ready for the next sprint planning |