🗓️ Sprint Planning – Advanced Analytics

Purpose

To define the work to be completed during the sprint, in line with the delivery plan.

Participants

All Advanced Analytics team members, stakeholders/subject matter experts/champions (optional)

Cadence

Bi-weekly Wednesdays (Start of each Sprint)

Format

• Clean up previous sprint taskboard:

  • Ensure all stories and tasks are closed.
  • For stories with partially completed tasks, create a Carryover Story with updated estimates and move remaining tasks into the new story. Close partially complete story

• Review team sprint capacity:

  • Enter team and personal days off.
  • Confirm daily capacity hours per team member.
  • Confirm total available hours for the sprint.

• Pull in new work:

  • Select stories that fit within each developer’s capacity.
  • Assign stories to individuals.

• Define sprint goal:

  • Confirm what the team aims to complete by the end of the sprint.

Guiding Principles

To ensure sprint planning is focused, efficient, and sets the team up for success:

• Stories Must Be Sprint-Ready

  • All stories must be clearly defined, estimated with story points, and include acceptance criteria.
  • Stories should be refined during backlog grooming to ensure they are actionable.

• Developer Preparation Is Expected

  • Developers should clean up their previous sprint work ahead of planning.
  • They should come prepared with preferences for upcoming stories based on project needs and capacity.

• Capacity Informs Commitment

  • Sprint commitments must reflect actual availability and working hours.
  • Avoid overcommitting, focus on sustainable delivery.

• Sprint Goals Provide Direction

  • Each sprint should have a clear, achievable goal aligned with business priorities and team capacity.

Expected Outcome

At the end of Sprint Planning there must be:

• A sprint goal clearly defined
• A selection of stories with estimates reasonably equal to capacity
• Each team member assigned a user story