> For the complete documentation index, see [llms.txt](https://www.lawfirm-operations.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.lawfirm-operations.org/publications-and-articles/agile-law-firm-workbook/6.-meetings/6.5.-a-sprint-meeting-setup-for-a-law-firm.md).
# 6.5. A Sprint Meeting setup for a law firm
These meetings occur at well-defined points in time, which could look as follows:
## Story
### Building habits
Would they do these meetings every week, Alice asks their colleagues, when they meet. Given the different timing requirements of the legal proceedings they ran, they decide that a rather short iteration interval would be advantageous, so they decide to do exactly that: weekly Sprints. Regularity will help them form their habits and the litigation often evolved so dynamically that a weekly planning would come in handy.
For the time being, the team sets up the following schedule of meetings: their team meeting will be extended from an hour to an hour and a half, and they’d have a quick Review, Planning and, once a month, Retrospective (all short) as well. If needed, the client could join the Review part, but often that might be a separate appointment.
As Agile methodology intends, they would continuously revisit their plan and adapt, if needed.
---
# 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://www.lawfirm-operations.org/publications-and-articles/agile-law-firm-workbook/6.-meetings/6.5.-a-sprint-meeting-setup-for-a-law-firm.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.