Sprint Planning Template &ZeroWidthSpace;

Authoritative sprint board and work items live in Azure DevOps Boards. This document is a planning reference. All work items referenced here must exist as ADO User Stories or Tasks with an AB#<id> before the sprint starts.

Sprint information &ZeroWidthSpace;

Field	Value
Iteration	`YYYY-Q<n>-S<m>`
Duration	[Start date] — [End date] (2 weeks)
Phase	[Phase 0 / 1 / 2 / 3 / 4 / 5]
Sprint goal	[One to two sentences describing the measurable outcome]
Scrum master	[Name]
Product owner	[Name]

Team capacity &ZeroWidthSpace;

Field	Value
Team members	[List names]
Available hours	[Total hours across team]
Planned velocity	[Story points]
Previous velocity	[Story points from last sprint, or N/A]

Sprint goal &ZeroWidthSpace;

[One paragraph describing what done looks like at the end of this sprint. The goal should be testable — either we hit it or we did not.]

Sprint backlog &ZeroWidthSpace;

Work items are listed by ADO priority. Create each item in ADO with full AC before the sprint starts.

Priority 1 and 2 items (must complete) &ZeroWidthSpace;

[ ] AB#[id] — [Verb-first title] — [Story points] — [Assignee]

Priority 3 items (scheduled sprint work) &ZeroWidthSpace;

[ ] AB#[id] — [Verb-first title] — [Story points] — [Assignee]
[ ] AB#[id] — [Verb-first title] — [Story points] — [Assignee]

Priority 4 items (stretch goals — only if Priority 3 is complete) &ZeroWidthSpace;

[ ] AB#[id] — [Verb-first title] — [Story points] — [Assignee]

Definition of done &ZeroWidthSpace;

A User Story is Done when all of the following are true:

[ ] All Acceptance Criteria met and verified by the person closing the item.
[ ] Code reviewed and approved; PR merged; commit includes AB#<id>.
[ ] Automated tests written and passing in CI.
[ ] Deployed to the dev environment.
[ ] No high-severity Snyk or CodeQL findings introduced.
[ ] ADO work item moved to Closed with a closing comment.

Risks and dependencies &ZeroWidthSpace;

Risk / Dependency	Mitigation / Owner
[Description]	[Mitigation and owner]

Sprint planning meeting notes &ZeroWidthSpace;

Field	Value
Date	[Meeting date]
Attendees	[Names]
Key decisions	[Decisions made]
Action items	[Follow-up tasks — create as ADO Tasks with AB#]