Explore

Sprint planning

Visualize the body of work the team will tackle in your next sprint

About the sprint planning template

The tempo of scrum is shaped by sprints. As soon as one sprint concludes, a fresh sprint kicks off. And the rhythm continues — a steady beat of development. By embracing sprints, teams foster predictability and accelerated learning.

This whiteboard template is ideal for detailing which user stories the team will prioritize in the next sprint. User stories or features should align with the product roadmap — it is important for the work to be tied to the value it will bring customers.

Make sure the team agrees on the effort required to complete the work and what success will look like. Outcomes might include your planned-to-done ratio of work, deployment quality, or even team happiness.

Best practices

Set the foundation for a successful sprint with a detailed plan.

Align on priorities Write a concise statement establishing the goal for the sprint to give the team a unifying focus. Add high-priority items from your product backlog to the whiteboard to clearly communicate the most important work.
Select user stories Pull user stories from the product backlog and break them down into smaller, actionable tasks. Discuss each one, ensuring that the team has a shared understanding of the requirements and acceptance criteria.
Estimate effort Use story points to estimate the effort required for each task. Make sure that the total number of points for the sprint is realistic based on the team's availability — factoring in planned time off and any other obligations.
Commit to the sprint plan At the end of the sprint planning session, the development team commits to completing the selected user stories and tasks. Be sure to refresh the board if any details change.

Use template