> 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/dao-consultancy/projects/project-kick-off/retrospective.md).
# Retrospective
You can facilitate a retrospective either at the end of the project or additionally as a review in the middle, in case the total duration exceeds 3-4 weeks.
A simple retrospective with uncertainty about the continuation of the project just needs a presentation and quick review to capture the learnings and ensure that all completed work has been accounted for and compensated for.
In case the project continues right away, you can continue with the following process:
* Write down all positives and negatives (7 minutes)
* Read out all positives individually (1 minute each)
* Read out all negatives individually (1 minute each)
* Vote on negatives (3 minutes)
* Brainstorm solutions for negatives (7 minutes)
* Vote on solutions (3 minutes)
* Discuss feasibility and delegate
#### Presentations
*`Present and capture - 3min each`*
Ask each team member to present the results of their work. In case anyone has comments, make sure there is a Miro board to capture notes during the presentation.
Ask if anyone has noticed a team member do unnoticed work that needs to be pointed out. In case there was, make a note of it to discuss retroactive compensation of the work later.
Make sure that all changes get passed on to the project manager/owner to accurately document in the Deep Teams application.
{% hint style="info" %}
If there is no certainty about continuing the work, you can stop here and start a new Kick-off workshop anytime in the future.
{% endhint %}
If project work continues and there is additional budget for the next sprint/project, take a note of the unnoticed work and who did it so you can include it in the budgeting at the end of the retrospective.
#### Brainstorm positives and negatives
`Duration: 10min`
Ask everyone to write down everything that stood out as positive (green notes) and everything you think that can be improved (red notes).
#### Read out positives and negatives
`Duration: 10min`
Let each participant read out the positives and negatives to provide a bit of context.
#### Brainstorm solutions
`Duration: 7min`\
Ask everyone to read through the negatives and place solution notes (blue) underneath in silence.
.jpeg?alt=media\&token=9423a988-01ae-4e43-89e5-6b10c08ffe95)
*`Vote: 7min`*\
Without discussion, ask all participants to read through the notes and place 5 dots on their favourite solutions.\
.jpeg?alt=media\&token=65e10de1-cd04-4f68-af1b-29ad68caeaaf)\
(you can also use the built-in Miro voting for this)
*`Delegate: 10min`*\
For the clearly actionable steps, delegate the work to the team. In difficult cases suggest improvements, create a governance proposal or reach out to the team lead to help solve the problem.
#### Duration & Budgets
*`Duration - 5 min`*
Decide when the next check-in will be. This could be in two weeks or a month. This could be a workshop session or retrospective session. During this time, the team can discuss any budget requirements for the project. After the decided duration, we will see the results of our collaboration and be able to decide how to re-start or continue. Remind the participants that the results of their commitment will also stay with them as part of their Deep Teams profile!
*`Budget - 5 min`*
Agree on whether a function needs compensation or a budget. Evaluating the duration of each function can act as a reference to define the compensation.
---
# 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/dao-consultancy/projects/project-kick-off/retrospective.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.