> For the complete documentation index, see [llms.txt](https://docs.deepwork.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwork.studio/teams-departments/software/projects/monthly-sprint.md).

# Monthly Sprint

## Goals:

* Progressing with the iteration of the Deep Teams product

## Hazards:

* More time is spent on bug fixing than actual progression of the app.
* Features might be irrelevant or bloat the software.

## Functions:

[Product Owner](/teams-departments/software/roles/product-owner.md)

[Frontend Engineering](/teams-departments/software/roles/frontend-engineering.md)

[Backend Engineering](/teams-departments/software/roles/backend-engineering.md)

[Software Product Design](/teams-departments/software/roles/software-product-design.md)

## Process:

1. Product owner creates tickets throughout the month for feature requests.
2. Product owner evaluates the current feedback from users and prioritises features.
3. Frontend and Backend engineers review the tickets and assess how implementation could affect other tickets or the existing application. Post feedback on Discord for review.
4. Product owner re-prioritises tickets based on engineering feedback.
5. In case of new design features, Product owner passes feedback and instructions to Software Product Designer to design screens. 
6. Product owner reviews results and passes them to the developer. Either directly or through a ticket in Notion.


---

# 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.deepwork.studio/teams-departments/software/projects/monthly-sprint.md?ask=<question>&goal=<endgoal>
```

`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.