> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/how-to-and-best-practices/managing-projects-and-time/plan-and-run-a-sprint.md).
# Plan and run a sprint
Sprints group tasks into a focused, time-boxed cycle so a team commits to a set of work, executes it, and reviews the result. This guide runs one sprint end to end.
## 1. Create the sprint
Create a sprint on the project and give it a name and a start and end date. The date range defines the cycle the team is committing to.
A sprint groups tasks into a time-boxed cycle
## 2. Add tasks to the sprint
Pull the tasks the team will tackle into the sprint. You can assign each task an owner and a time estimate so the planned workload is visible before the cycle begins. Tasks that aren't ready can stay out and be added to a later sprint.
## 3. Start the sprint
Starting the sprint marks the cycle as active. From here the sprint becomes the team's working set, and you can filter any task view down to just this sprint's work.
## 4. Track progress
Follow the work as it moves using whichever view suits the team:
* **Kanban View**—drag tasks across status columns to see flow at a glance.
* **List View**—a sortable table for detailed tracking and bulk updates.
Kanban and list views of the sprint's tasks
Filter by sprint to keep the board focused on the current cycle. A **Calendar View** is also available for date-based planning across the cycle.
Calendar view for date-based planning
To see where these views live on screen, see the [Project Suite screens](https://docs.we360.ai/reference/work-and-time-management/user-interfaces/portal/project-suite/projects).
## 5. Complete the sprint
When the cycle ends, complete the sprint. Work that was finished is captured with the closed sprint; incomplete tasks can be carried over into the next sprint so nothing is lost between cycles.
## 6. Review and plan the next cycle
Use the completed sprint to review what shipped and what rolled over, then start the next sprint with the carried-over work already in place.
{% hint style="info" %}
For what statuses, estimates, and story points mean, see the [Projects & Tasks reference](https://docs.we360.ai/reference/work-and-time-management/product/work-and-time-management/projects-and-tasks).
{% endhint %}
---
# 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://docs.we360.ai/how-to-and-best-practices/managing-projects-and-time/plan-and-run-a-sprint.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.