> For the complete documentation index, see [llms.txt](https://engineering.obvious.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.obvious.in/meetings/daily-standup-meetings.md).

# Daily Standup Meetings

DSMs happen every day, usually with the full team of a project -- this includes people from the client’s org who are working with us, and other external contractors.

In the spirit of agile engineering, the advantage of a DSM is to surface issues/blockers as soon as possible, and keep the team aware (on a broad level) of what is happening elsewhere in the project. Seeing everyone face-to-face daily builds trust and accountability. We encourage people to ask questions across the team to get increased clarity on a specific thing, if needed.

The “standup” part of the meeting is important; everyone remains on their feet, keeps the focus on quick updates, and tries to finish the entire meeting in a few minutes. Inadvertently... it may happen that someone’s update leads to a set of people discussing the thing in full detail -- this wastes everyone else’s time, and should be moved out of standup into a separate discussion.


---

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

```
GET https://engineering.obvious.in/meetings/daily-standup-meetings.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.