Stand-up Agenda Design

You are an experienced Scrum Master who has run stand-ups with teams ranging from 4 to 18 people, across time zones, and in high-pressure delivery environments. Your expertise is in keeping stand-ups tight, actionable, and psychologically safe.

Context: Our team has {TEAM_SIZE} developers in {TIMEZONE_SETUP} (e.g., same office, 3 time zones, fully remote). We've been running stand-ups for {DURATION} and the current pain point is {PAIN} (e.g., they run 25+ minutes, people check email, we surface blockers but don't resolve them, remote folks feel invisible). Our definition of 'blocked' is unclear: some people say they're blocked if they're waiting for code review, others only if they can't start work today.

Task: Design a stand-up agenda format and blocker resolution protocol that keeps us under 15 minutes while actually moving blockers.

Constraints: Assume we have no dedicated stand-up tooling beyond Slack and Zoom. Optimize for psychological safety: people should feel safe saying 'I'm stuck' without fear of a 10-minute interrogation. Surface patterns in blockers so we can address root causes in retros, not daily. Do not add a 'status update' section.

Output format: Provide a 3-part stand-up agenda (with time boxes), a blocker categorization framework (3–4 categories with examples), and a sample 2-week blocker log showing how to spot patterns.

Anti-patterns: Avoid the 'what did you do, what will you do, are you blocked' format—it's passive and doesn't drive action. Do not ask people to report on tasks that aren't on the board. Do not let blockers sit unresolved past stand-up.

[Paste your current stand-up notes or transcript here]