> For the complete documentation index, see [llms.txt](https://help.usehaystack.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usehaystack.io/guides/daily-standups.md).

# Daily Standups

Haystack helps development teams run more effective daily standups by providing data-driven insights.

## Better Daily Standups with Haystack

{% embed url="<https://www.loom.com/share/efa6cd2a9e6c41e1ac3dca812fc55e1d?sid=29122de6-3192-4316-be35-84cfdc2c75ee>" %}

### Making Daily Standups Work Better

Development teams need efficient daily standups. Even with well-defined sprint goals, teams face daily challenges like unexpected bugs, changing requirements, and coordination needs that can derail progress.

As teams scale, these challenges multiply. Leaders need to track multiple workstreams, manage dependencies, and ensure clear communication. While traditional standups help, they often lack the structure needed to effectively address these day-to-day issues.

Haystack transforms these daily meetings into data-driven strategic sessions that help you answer 3 critical questions for your daily standups:

1. Are we on track to meet our sprint goals?
2. What's blocking progress?
3. Are priorities clear and resources balanced?

Haystack combines Git and Jira data with intuitive workflows to help you quickly identify blockers and track sprint progress. Here are the key capabilities:

* Track sprint progress with [real-time activity changes](https://help.usehaystack.io/features/issues)
* Identify and resolve blockers through [alerts](https://help.usehaystack.io/features/alerts)
* Tailor sprint direction with [workflow insights](https://help.usehaystack.io/features/issues#h_f7d69cca4d)

Haystack empowers teams to transform daily standups from basic updates into strategic discussions that drive better engineering outcomes and accelerate sprint progress.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.usehaystack.io/guides/daily-standups.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.