> For the complete documentation index, see [llms.txt](https://docs.7ft10.com/flow-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.7ft10.com/flow-system/topics/planning/sprint-iteration-planning.md).

# Sprint / Iteration Planning

{% hint style="success" %}
***We use this to** set the team up for success with clear goals and expectations **so that we can** all be on the same page about what the iteration is trying to achieve.*
{% endhint %}

## Overview <a href="#howtoguide-sprintplanning-overview" id="howtoguide-sprintplanning-overview"></a>

Sprint Planning is the first action in the sprint and sets it up for success.

The whole Scrum team, plus relevant stakeholders and SMEs, should collaborate in this ceremony.

<figure><img src="https://1491389417-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZKVth8lQoa81KxznCuDw%2Fuploads%2FQ2s5MHROPHo2YFbIbacE%2Fimage.png?alt=media&amp;token=fb3dbfbd-d81a-4dde-ab7c-aedad288ffe0" alt=""><figcaption></figcaption></figure>

## Input <a href="#howtoguide-sprintplanning-input" id="howtoguide-sprintplanning-input"></a>

* Availability
  * Number of days in the sprint
  * Team members leave or not sprint-related commitments
* Capability
  * Team velocity
  * The skills required to deliver a Story&#x20;
* Constraints, issues and risks
  * Anything that could block or delay the sprint&#x20;
  * Any dependencies from other teams
* Product Backlog
  * Unfinished work from the previous sprint that is still a priority
    * Can be pushed to the Sprint Backlog and reviewed during the planning
  * Action points from Sprint Retrospective
    * It is recommended only to add action points that will affect the velocity of the board.&#x20;
  * Product Backlog Items, preferably in order of priority
* Quarterly roadmap
  * PO reinforces the bigger picture of how the items in Backlog relate to roadmap items.

## Outputs <a href="#howtoguide-sprintplanning-outputs" id="howtoguide-sprintplanning-outputs"></a>

* Sprint goal
  * Why are we running this sprint
  * PO proposes a Sprint Goal that provides focus, and the team collaborate to finalise it&#x20;
  * The sprint goal drives the decisions during the sprint&#x20;
* Sprint backlog
  * A list of Stories done within the Sprint accomplishing the Sprint goal
  * The Scrum team refines the list to a comfortable level of confidence in delivering it
* Plan for the sprint - At least a plan of attack for the first half of the sprint
  * Break the stories further into daily tasks
  * Take into consideration extra time for cross-skilling
  * A good ballpark is to commit to what can be done in 8 days, assuming a day is used on Sprint Ceremonies and other meetings and another day for routine tasks and contingency.

## Timebox <a href="#howtoguide-sprintplanning-timebox" id="howtoguide-sprintplanning-timebox"></a>

The Scrum Guide recommends 8 hours for a four weeks sprint, meaning up to four hours for a two weeks sprint. Instead of doing a long session and risk losing engagement as time passes, a better approach is to set up specific story elaboration sessions, removing story clarification, refinement and estimation from the sprint planning ceremony.

If all stories are "ready", meaning they are elaborated, refined, discussed, understood and estimated at the beginning of the Sprint Planning, the team can plan in an hour.

## Roles and Responsibilities <a href="#howtoguide-sprintplanning-rolesandresponsibilities" id="howtoguide-sprintplanning-rolesandresponsibilities"></a>

<table><thead><tr><th width="122.33333333333331">Role</th><th>Responsibilities</th><th>Deliverables</th></tr></thead><tbody><tr><td>Scrum Team</td><td>Commit to an increment to be delivered within the Sprint</td><td>Sprint Goal, Sprint Backlog, Sprint Plan</td></tr><tr><td>Development Team</td><td><p>Are intimate with the stories that are likely to be included in the sprint</p><p>Collaborate to define the most efficient way to deliver the increment</p><p>Understand the value the Sprint will achieve</p></td><td>Commitment to deliver the increment</td></tr><tr><td>Product Owner</td><td><p>Assure the Scrum Team understand the goal for the sprint</p><p>Assure the Development Team understand the Stories</p><p>Provides a refined set of stories ready for planning</p><p>Identifies the business objective they ideally would like to see accomplished during the sprint.</p></td><td>Prioritised and elaborated Product Backlog Items</td></tr><tr><td>Scrum master</td><td><p>Assure the Scrum team is ready for Sprint Planning.</p><p>Keep the ceremony on topic.</p></td><td><p>Scrum team ready to plan</p><p>Safe environment </p></td></tr><tr><td>Subject Matter Expert</td><td><p>Provide support to clarify Stories.</p><p>Confirm if the planned solution returns the expected value.</p></td><td><br></td></tr></tbody></table>

## Agenda <a href="#howtoguide-sprintplanning-agenda" id="howtoguide-sprintplanning-agenda"></a>

<table><thead><tr><th width="127.33333333333331">Timebox (minutes)</th><th width="155">Owner</th><th>Description</th></tr></thead><tbody><tr><td>15</td><td>Scrum master</td><td><ul><li>Confirm availability for the sprint</li><li>Review the unfinished stories on the last sprint and close that sprint</li><li>Review the retro action points and estimate them</li></ul></td></tr><tr><td>30</td><td>Product Owner</td><td><ul><li>Reminds the Scrum team about the Quarterly Goals</li><li>Proposes the Sprint Goal and collaborate with the Scrum team to define the stories that will achieve the goal</li></ul></td></tr><tr><td>60</td><td>Development Team</td><td><ul><li>Collaborate to define a plan of attack, breaking down stories, highlighting possible blockers.</li><li>Define commitment for the sprint</li></ul></td></tr><tr><td>15</td><td>Development Team</td><td><ul><li>Present the plan to the PO and SM</li></ul></td></tr><tr><td>30</td><td>Scrum team</td><td><ul><li>Review and fine-tune the plan</li><li>Confidence vote</li><li>Start the Sprint</li></ul></td></tr></tbody></table>

## References

Scrum Guide: <https://scrumguides.org/scrum-guide.html#sprint-planning>