Generate Daily Standup Meeting Templates

Daily Standup Template Expert is a prompt for creating and facilitating daily coordination meetings. It offers a standard three-question format plus variations for board review, remote teams, bug triage, and release week. The guiding principles are transparency about progress, inspection of obstacles, and adaptation when new information changes the team's plan.

The standard template records the date, duration, start time, facilitator, attendance, completed work, today's priorities, blockers, action owners, due dates, and sprint progress. Updates should connect to the sprint goal, identify dependencies, and describe specific work rather than broad activity.

Use it when a team needs a consistent, short meeting that surfaces coordination needs and assigns follow-up work. Use a suggested fifteen-minute limit for teams up to nine people, one- to two-minute individual updates, and additional time for larger groups. These are template guidelines to adapt to the team's size and context.

The meeting should not become a detailed technical discussion or a manager reporting exercise. Move longer topics to a parking lot and arrange a separate conversation with the relevant people. A filled template is a record of what participants reported, not independent verification that a task or release is complete.

The three standard questions ask what was completed yesterday, what will be worked on today, and what prevents progress. Today's list is limited to two or three items in the source. Action entries carry both an owner and a due date.

Walking the Board reviews work from right to left, starting with completed or review-ready items before progressing through active, upcoming, and blocked work. It exposes ownership, dependencies, and obstacles at the item level instead of relying entirely on individual updates.

The remote variation collects asynchronous updates before a short synchronous discussion of blockers and dependencies. It includes meeting and backup channels, working location or hours, and a parking lot. The bug-triage variation adds critical issues and counts of opened, closed, open, and regression bugs. The release-week variation adds readiness checks for code freeze, quality sign-off, documentation, deployment scripts, risks, and mitigation plans.

Open by restating the sprint goal, remaining time, urgent announcements, and attendance. Keep a consistent update order, capture blockers, and close by confirming owners and follow-ups. Rotate facilitation, invite quieter participants, and make raising problems safe. Asynchronous contributions offer another participation route.

The weekly retrospective asks what works, what needs improvement, and which one change to try next. It tracks average and longest meeting duration and participation. Adapt terminology, project sections, time zones, and links to existing Jira or Trello workflows; those mentions do not establish automatic integrations. Review the template monthly while preserving a predictable structure.

The prompt is for agile teams and facilitators who want daily meetings to produce clear coordination decisions, visible blockers, and accountable next actions.