> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-planning-items.md).
# Sprint Planning Items
## Video Version
Coming soon
## What are Sprint Planning Items?
Sprint planning items are documentation that an Agile team delivers when they are operating with the Scrum method. Each time they perform a sprint, they discuss:
1. The priorities based on the [project roadmap](broken://pages/a7rLakbW5PEx99fKbQ5p)
2. The "Sprint Goals": outcomes to achieve by the end of the next sprint
3. The "Sprint Items": independent tasks involved to achieve the sprint goals
4. The ["Sprint Do'ers"](/agile-training-portal/agile-handbook/agile-methods/scrum-method/scrum-team-functions.md): people who are committed to finish the work together.
Here's an example of a result of sprint planning:
## Why are Sprint Planning Items Valuable?
Sprint planning items are valuable because they create clarity and expectations about what the team is committing to. They enable teams to rally around the same shared outcomes to achieve, no matter how they choose to achieve them as a self-organized team.
## How are Sprint Planning Items Made?
Teams get together, review the [backlog ](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/backlogs-and-kanban-boards.md)and [project roadmap](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/project-phase-roadmaps.md), and decide priorities for the sprint together. Tasks they choose should already have [product requirements](broken://pages/jF6xTBxNmUkkZtn2f909) that are refined so that they are ready to be worked. Teams may need to run a [prioritization activity](broken://pages/lZOR35UrpHjZkaovTLYu) before choosing their sprint items.
## Who Maintains Sprint Planning?
The Scrum Master function runs and facilitates sprint planning based on the [backlog management](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/backlogs-and-kanban-boards.md) that the Product Owner function performs.
## Sprint Planning Workshop
Here's a Workshop Template your team can use before a project and during projects to outline the sprint goals, sprint tasks, and assigned team member responsibilities.
{% embed url="" %}
This workshop template helps teams plan a sprint with sprint goals, sprint tasks, and sprint assignees. Credit: Tech Fleet .
{% endembed %}
## When Should Teams Build their Sprint Planning Items?
[Before every sprint](/agile-training-portal/agile-handbook/agile-methods/scrum-method/scrum-meetings.md), the team gets together to plan their upcoming sprint, and revisit the [project roadmap](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/project-phase-roadmaps.md).
## How to Build Sprint Planning Items
### Here are the steps:
1. Get together as a full team.
2. Review the project roadmap to go over what you estimated to take on.
3. Prioritize sprint items.
4. Identify the sprint goals, the shared outcomes to achieve for the sprint.
5. Choose the sprint items.
6. The team self-commits to the work, and chooses how they want to be involved.
## Head to the Next Lesson
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-planning-items.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.