Back to all templates

SAFe® Sprint planning

Help teams in the agile release train (ART) create an achievable sprint plan.

Use template
SAFe® Sprint planning large

About the SAFe sprint planning template

Create a high-level sprint plan for each team in your ART. This step in the program increment (PI) planning process is key to aligning everyone on what needs to be delivered and when in order to achieve the overall product or solution vision.

Use this template during team breakout sessions. Customize the sprint schedule to reflect the number of iterations in your PI. (A common approach is four iterations for working on committed features, with one iteration set aside for innovation and planning.) Capture your PI objectives at the top of the board and then review the backlog of assigned features. Break each feature down into smaller user stories, placing them into the appropriate sprint to create a draft plan for the PI.

Share your sprint plan with other teams for feedback. Discuss any questions or concerns related to architecture, scope, and resource constraints. The team can then adjust the details, listing out any risks and dependencies before committing to the overall PI plan. Note that this template is one component of the SAFe PI planning template series, which also includes a PI board, ROAM board, and retrospective template.

Best practices

Use this template during PI planning — so each team can plan out what needs to be delivered and when.

  1. Prepare for team breakouts Adjust the template to match your iteration schedule for the PI. Create a sprint planning board for each team in the ART to provide a dedicated space for collaborating during breakout sessions.

  2. Define the work Capture the features that are assigned to your team for implementation in the PI. Visualize the overall objectives that relate to these features at the top of the sprint planning board to stay focused on the bigger purpose.

  3. Create a sprint plan Break each of your features down into individual user stories and assign them to a sprint. Thinking through all of the technical requirements and dependencies at this stage in the planning process helps you sequence the work correctly.

  4. Commit and regroup Note any risks or blockers in the ROAM board on the right. Once your team feels confident that they can deliver the assigned work on time, share your sprint plan with the broader group to finalize the overall approach for the PI.

Use template