Sprint planning notes template
Give the sprint a clear purpose and an honest boundary. Capture why the work was selected, what it depends on, and what stays out.
Free template + filled example. No account required. How to use the Skill
- Made for
- Engineering & product
- Suggested conversation
- 45–90 minutes
- Take it with you
- Markdown · Prismical Skill
See the finished note.
Use this while a team selects work for its next cycle. The fictional example covers invitation reliability and a dependency on email configuration. It records a plan, not a delivery guarantee.
Notes / worked exampleSprint plan · Invitation reliability
Sprint goal
Make it easier for workspace owners to recover from failed invitations.
Capacity & assumptions
Casey is away Friday. The team has not estimated the resend flow yet.
Selected scope
Add failed-invitation status and a resend control. Acceptance: owners can see a failure and request another invitation.
Dependencies & risks
Resend depends on email configuration confirmation from the infrastructure team. Confirmation is still pending.
Out of scope & trade-offs
Bulk invitations are deferred. If email configuration slips, prioritize visible failure status.
Next actions
Casey will ask infrastructure for confirmation today. Resend estimation owner: not assigned.
Read the source dialogue for this example
- Casey: Our goal is to help workspace owners recover from failed invitations. I am away Friday.
- Drew: Let’s include failed-invitation status and a resend control. We still need to estimate resend.
- Casey: Owners should see a failure and be able to request another invitation.
- Drew: Resend depends on infrastructure confirming the email configuration. That is pending.
- Casey: I will ask infrastructure today. Bulk invitations should stay out of this sprint.
- Drew: If configuration slips, we prioritize the visible failure status.
Start with a blank page.
Keep the useful structure.
Each field earns its place. Use the prompts as reminders, then replace them with your own meeting evidence.
Sprint goal
Describe the user-visible outcome in one sentence. Avoid turning a list of tickets into the goal.
Capacity & assumptions
Record known availability and uncertainty. Do not silently convert a rough estimate into a guaranteed completion date.
Selected scope
List the work agreed for the cycle and the acceptance conditions that explain when it is complete.
Dependencies & risks
Name the external condition, its owner if known, and the consequence of delay. Keep an unresolved dependency visible.
Out of scope & trade-offs
Record what the team intentionally deferred. A clear exclusion prevents the plan from expanding through casual follow-up.
Next actions
Capture the planning follow-up, with dates only as stated. Keep work selection distinct from individual acceptance of a task.
# Sprint planning notes template Date: [add date] Participants: [add names] Purpose: [add purpose] ## Sprint goal [Describe the user-visible outcome in one sentence. Avoid turning a list of tickets into the goal.] ## Capacity & assumptions [Record known availability and uncertainty. Do not silently convert a rough estimate into a guaranteed completion date.] ## Selected scope [List the work agreed for the cycle and the acceptance conditions that explain when it is complete.] ## Dependencies & risks [Name the external condition, its owner if known, and the consequence of delay. Keep an unresolved dependency visible.] ## Out of scope & trade-offs [Record what the team intentionally deferred. A clear exclusion prevents the plan from expanding through casual follow-up.] ## Next actions [Capture the planning follow-up, with dates only as stated. Keep work selection distinct from individual acceptance of a task.]
Make it part of the meeting.
Before · bring ready decisions
Review the proposed goal, known dependencies, and team availability. Bring enough context to discuss scope without pretending every estimate is settled.
During · record the trade-off
When the team adds something, ask what it displaces. Capture acceptance conditions in plain language so someone reading later understands the intended result.
After · reconcile the plan with the board
Check that selected work, owners, and exclusions agree with the team’s work tracker. This note explains the decision; it does not automatically create or update tickets.
What to watch for
- Presenting tentative scope as a promise to stakeholders.
- Hiding a dependency inside a ticket description.
- Treating unassigned estimation as already completed work.
Turn the template
into a Prismical Skill.
Import the file
Download the Skill JSON above. In Prismical, open Settings → Skills → Import and select the file. This downloads a file; it does not install anything automatically.
Run it on a note
Open the note with your meeting transcript. Run the imported Skill from the note dock. It asks for this template’s sections and appends the result for review.
Check before sharing
Verify quotes, owners, dates, and missing context against the transcript. AI can make mistakes. Keep the original note and follow your team’s sharing policy.
A few useful answers.
Practical details before you use this resource.
Should I include story points?
Include them if your team uses them and the estimates were actually agreed. The template does not require points; the goal, capacity assumptions, dependencies, and scope choices are useful with other planning methods too.
Does a selected task need an owner immediately?
That depends on how your team works. Record “not assigned” when it is true. Do not infer an owner from the person who described the task or raised the dependency.
Keep the work moving.
Useful next steps for the conversation you are preparing for.
Sprint retrospective notes template
Run a retrospective with observations, contributing factors, and a small measurable experiment. Free notes template with a filled example and Prismical Skill.
Explore resource TemplatesProject kickoff meeting notes template
Align a project around outcomes, scope, decision owners, dependencies, and first actions. Free kickoff notes template, worked example, and Prismical Skill.
Explore resource Free toolsFree meeting minutes generator
Turn pasted meeting text into a reviewable minutes draft with discussion excerpts, decision candidates, and actions. Free browser-only tool; no account needed.
Explore resourceBring your next conversation
into Prismical.
Capture the conversation, keep the transcript beside your notes, and reuse a Skill for the output you need. Review the result before you share it.