Reference for the Sprint Planning meeting structure, agenda, and preparation requirements.

Meeting goal

Finalise the Sprint scope based on current capacity, ensuring every work item is well-defined and ready for delivery.

Agenda

Close preceding Sprint

Formally conclude the previous iteration and transfer any uncompleted work items to the new Sprint.

Confirm Sprint duration

Verify the standard Sprint length (e.g., 2 weeks), adjusting for any holidays or team availability.

Agree on Sprint goals

Collaborative discussion between the Product Owner and Development Team to formulate 1–3 concise, high-level goals.

Determine team capacity

Individual and aggregate assessment of story point capacity based on availability and historical performance.

Backlog review & assignment

  • Present all stories and tasks to the team to ensure the scope is well-defined.
  • Review acceptance criteria and address technical challenges or dependencies.
  • Review and assign unresolved bugs from the Product Backlog.
  • Assign work items to individuals based on capacity and expertise.

Logistics & collaboration

Establish development pairs and assign shared coding machines.

Final commitment

Conduct a final review of the backlog and formally start the Sprint.

Preparation

To be completed prior to the meeting.

Product Team

  • Ensure all Example Mapping sessions have been completed to clarify requirements.

Development Team

  • Create a Sprint Design & Architecture task.
  • Draft regression test plans for all components and areas impacted by this Sprint.

Agile Coach

  • Ensure all “flagged” work items (blockers) are resolved or removed from the backlog.

Note: Please review the draft Sprint Backlog and your individual availability (PTO/holidays) before the session.

Updated: