Stand-Up Agenda: A 15-Minute Template for AI Dev Teams

A good stand-up agenda has three parts for each person: what shipped, where you’re stuck, and what you learned. Keep the meeting to 15 minutes and move any longer discussion to a follow-up with only the people it concerns. For a remote team, run it async in Slack, written from what people actually did rather than from memory.

Here is the template:

Daily stand-up (15 minutes)

1. Shipped: what merged or moved forward since yesterday (link the PRs)
2. Stuck: what is blocking you, and who can help
3. Learned: one thing about your tools or the codebase worth passing on

Parking lot: topics for a follow-up after the meeting

Why the classic three questions fall short

“What did I do yesterday, what will I do today, what’s blocking me” came from Scrum, but Scrum itself no longer requires those questions. The 2020 Scrum Guide describes the Daily Scrum as a 15-minute event to inspect progress toward the Sprint Goal and says developers “can select whatever structure and techniques they want” (Scrum Guide).

The old questions also hide most of what matters on a team that codes with AI agents. “Making progress on the new feature” can mean very different things:

• An agent run went sideways and someone spent two hours undoing it.
• Someone found a way of working with the agent that saved an afternoon.
• The blocker isn’t a person or a bug but a tool, for example an agent that keeps using an outdated version of an API.

The three-part agenda brings those out without making the meeting longer.

The agenda: shipped, stuck, learned

Shipped. What merged or moved forward, with links. “Merged the retry fix, #1412. The agent wrote the tests and I reviewed them.” Links beat descriptions: anyone who wants detail can click.

Stuck. What’s in the way, and who can help. “The agent keeps writing code for v1 of our payments SDK. I need half an hour with someone who knows v2.” A blocker named with a person attached gets resolved after the meeting.

Learned. One thing worth passing on. “On the database migration, asking the agent for a plan first saved a rewrite.” Or: “The flaky checkout test is a timezone bug, not the network.” Skip it on days with nothing to say.

Agenda point	Classic stand-up	This agenda
Yesterday	“I worked on ABC-123.”	Shipped: “Merged #1412, the retry fix.”
Today	“I’ll keep working on ABC-123.”	Implied by what’s still open; mention only changes
Blockers	“Blocked by staging.”	Stuck: “Staging is down; Priya, can you look after this?”
Learning	Not asked	Learned: “Plan mode first on migrations saved a rewrite.”

How to run it in 15 minutes

Keep it to 15 minutes. The timebox forces short updates and pushes problem-solving into smaller follow-ups, which is where it belongs.

• Same time every day. Early enough that people haven’t started deep work, late enough that everyone is online.
• One facilitator, rotated. Rotate the role daily or weekly. The facilitator keeps time and steers tangents to the parking lot; they’re not the boss.
• Park anything longer than a minute. “Let’s take that right after with just the three of you.”
• It’s for the team, not a report to a manager. Questions about timelines or individual tickets go to another meeting.

Common ways it goes wrong, and the fix:

• Someone dives into a technical problem. The facilitator: “That sounds important. Can you and Sam pick it up right after this?”
• A vague update (“I worked on the API, and I’ll keep working on it”). The facilitator: “Anything merged, or anything in your way?”
• A manager starts asking for ticket status. The facilitator: “Good question. Can we take it to the project sync so we keep this moving?”

Async stand-ups for remote teams

Across time zones, a written stand-up in Slack often works better than a video call. Each format has a cost:

• Live video keeps the human connection and lets small blockers get solved on the spot, but it’s hard to schedule across time zones.
• Async in Slack lets everyone post when their day starts, but you lose the quick back-and-forth.

Many teams mix the two: a live stand-up two or three days a week and async updates on the others. Pick one schedule and keep it, so people know what to expect.

For async, use the same three parts in a daily thread, posted by a fixed time. The weak point is the writing: people post vague updates or forget. Async teams need the standup written from real activity, not reconstructed from memory at the end of the day.

Have the standup written from PRs

Zest writes each engineer’s standup at 6pm in their time zone, from that day’s coding-agent sessions (Claude Code, Codex, Cursor, Copilot Chat and others) and pull requests, and posts it to Slack or sends it by email. Nobody types an update, and the Shipped part comes with links to the pull requests.

On Fridays, Zest’s Team Standup rolls up the week for the whole team: the AI stack worth sharing (the skills and practices that spread), the week’s wins, and up to three moves to ship more. That covers much of the Learned part, so the live meeting can spend its time on what’s stuck.

Keep what the team learns

The Learned part is only worth something if it outlasts the meeting. When the same tip comes up twice, write it down where people and agents will find it: a team doc, the project README, or the instruction file your coding agent reads (such as AGENTS.md or CLAUDE.md). A recurring blocker is a signal too: if three people are stuck on the same tool in a month, fix the tool or write the guide, rather than unblocking each person one at a time.

Frequently asked questions

How long should a daily stand-up be?

Keep it to 15 minutes. The Scrum Guide sets the Daily Scrum at 15 minutes, and the limit keeps updates short and pushes problem-solving into smaller follow-ups. If it regularly runs over, move discussions to a parking lot and take them after the meeting.

What should a stand-up agenda include?

For each person: what shipped (with links), where they’re stuck and who can help, and optionally one thing they learned. End with a parking lot of topics for follow-up conversations. The Scrum Guide doesn’t prescribe the questions, so pick a structure that keeps the team focused on progress toward its goal.

Can a stand-up work asynchronously?

Yes. Post the same three parts in a daily Slack thread by a fixed time. Async stand-ups work best when the update is written from real activity, such as the day’s pull requests, instead of from memory.

Who should run the daily stand-up?

Anyone on the team. Rotating the facilitator daily or weekly keeps people engaged, and the facilitator’s job is only to keep time and move tangents to the parking lot.