How Sprint Planning Works
If your project uses Agile methodology, it is structured into sprints — short, focused delivery cycles (typically 2 weeks). Sprint planning is the meeting at the start of each sprint where we decide what will be built.
Before Sprint Planning
Your Project Manager and Lead Engineer will review the product backlog (the prioritised list of all remaining work) and select items that can realistically be completed in the sprint, based on the team's capacity.
The Sprint Planning Meeting
Sprint planning is usually a 1-hour meeting at the start of each sprint. Attendees: your Project Lead (or day-to-day contact) and the Progressive Robot project team.
In the meeting, we:
- Review what was completed in the previous sprint
- Present the proposed sprint backlog (what we plan to build this sprint)
- Confirm acceptance criteria for each item with you
- Raise any dependencies or blockers we are aware of
- Agree the sprint goal — the primary outcome we are working toward
Your Role in Sprint Planning
Come prepared to:
- Confirm priorities if there are competing items in the backlog
- Answer clarifying questions about requirements
- Confirm any dates that are relevant (e.g. external demos, launches, integrations)
After Sprint Planning
You will receive a sprint plan summary in the portal outlining what is committed for the sprint. Mid-sprint changes are strongly discouraged — they disrupt the team and reduce output. Save new requirements for the next sprint planning session.