# Sprint prep

* **Outline:** Ensure that the team is ready to start the next Sprint.
* **Goal:** Decide which Users Stories can be worked on.
* **Duration:** 15-30 minutes.
* **Frequency:** Before starting a new Sprint.

## How-to

1. Open the Project Board and Issue list
2. Quickly assess current Sprint progress status
3. Look for assigned tasks that have become irrelevant or outdated
   1. For irrelevant tasks: discard them on the next Sprint Planning
   2. For outdated tasks: update the necessary information before the next Sprint Planning
4. Agree on a rough estimate of what should be achievable on the next Sprint

   *Note: mind the potential amount of work that will carry over before commiting to new tasks.*
5. Make sure all User Stories to be started have all the necessary details, including design decisions.
6. Assess availability for all necessary team members (all necessary skills)


---

# Agent Instructions: 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:

```
GET https://handbook.catalpa.io/the-catalpa-handbook/5.-project-and-product-cycle-management/5.4-post-contract-implementation/stage-3-refine-and-release/scrum-methodology/sprint-prep.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.