Keep your ten-person standup useful when Jira writes the digest

Jira added the Delivery Agent as a built-in AI agent powered by Rovo. For a ten-person team, the Daily Standup digest is the part that changes the meeting. The Jira Summer 2026 release was scheduled to reach full availability on Jira Cloud before August 2026 ended. Over the past 12 months, Jira work-item loading speed improved by 57%, lists and search improved by 60%, and company-managed boards and backlogs improved by 48% and 16%, respectively. The speed does not fix the meeting.

The digest earns its place by removing status

Standups can drift into routine progress reporting, and data can remain siloed. The Daily Standup template automatically sweeps a Jira board and surfaces work that is moving, blocked, or needs a nudge. That job belongs to the digest. It should not own the judgment about what the team should do next.

• Turn on the Daily Standup template in the Summary view, where Jira makes three pre-built, AI-powered Delivery Agent automation templates available: Daily Standup, Delivery Health Check, and Stakeholder Status Summary. The test is that the digest arrives before the meeting, and nobody opens a ticket just to say what they did yesterday.
• Put the digest link in the calendar invite, and tell the team it is not a performance record. The signal is people reading it before the meeting, and a blocked ticket is treated as a prompt, not a verdict.
• Assign the digest the status job only. It should cover the board, not the people. Success looks like an agenda line: status is already collected, so the meeting starts with what the digest missed.
• Keep the Delivery Health Check template for a separate review, not for the standup itself. It identifies overdue items, stalled work, and early delivery-risk signals. The habit is to use it when the sprint is under pressure, not as a repeated status report every morning.
• Use the Stakeholder Status Summary for people outside the team, not for the standup. The result is a distinct update that does not pull the team into a longer meeting.
• Reserve the daily meeting for blockers to the sprint goal and coordinated unblocking of the riskiest work, not routine progress reporting. The common mistake is to let the digest become the only place risk is named. The proof is a named risk that is not in the digest, and a decision about who removes it today.

Keep it read-only during the meeting. If someone wants to add a ticket, they can do it after. The digest should be a reference, not a working document. That keeps the conversation on risk instead of data entry.

The meeting keeps the risk call

87% of teams use Scrum, a framework that includes a daily stand-up. A sprint timebox exists to limit work-in-progress, push teams to finish, integrate continuously, and surface risk early. The digest helps by removing the status report. It does not help if the team stops noticing what the board misses.

Signals from any stage can lead to work being reordered or redesigned. The meeting needs a decision, not another summary. If the digest says everything is moving, the team still has to say whether the riskiest item is actually moving toward the goal.

Make the boundary visible before the next sprint

In Scrum, converting a sprint review into routine progress reporting weakens the cycle by blurring its separate conversations. The same mix-up can happen in the standup. In Agile marketing, renaming status meetings standups and adopting a tool like Jira can be a cosmetic change rather than real agility. Product teams make that mistake when the digest becomes the whole ritual.

Write the boundary in the meeting notes, not in a policy document. The team should see it before the digest is read, and it should survive the awkward week when people still want to report status.

The digest replaces status collection. It never replaces calling out unraised risks or re-prioritizing work.