daily-standups

spjoshis's avatarfrom spjoshis

Master daily standup facilitation with focus, time management, and effective patterns for team synchronization and impediment identification.

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 30, 2025
[Meeting Productivity]

When & Why to Use This Skill

This Claude skill streamlines daily standup facilitation by providing structured patterns for team synchronization, effective time management, and rapid impediment identification. It helps Agile teams maintain momentum toward sprint goals through standardized reporting, 'walking the board' techniques, and disciplined time-boxing to ensure high-efficiency team alignment.

Use Cases

  • Facilitating 15-minute time-boxed daily syncs to ensure team alignment and maintain focus on sprint goals.
  • Identifying and documenting blockers or impediments early in the day to prevent project delays and resolve issues offline.
  • Implementing 'Walking the Board' techniques to visualize task progress across different stages from To-Do to Done.
  • Standardizing team updates using the core three-question format: yesterday's achievements, today's plan, and current obstacles.
  • Improving remote team collaboration by providing a consistent structure for virtual standups and real-time taskboard updates.
namedaily-standups
descriptionMaster daily standup facilitation with focus, time management, and effective patterns for team synchronization and impediment identification.

Daily Standups

Facilitate focused daily standups that synchronize the team, identify blockers, and maintain momentum toward sprint goals.

When to Use This Skill

  • Daily team synchronization
  • Progress updates
  • Impediment identification
  • Re-planning work
  • Maintaining focus
  • Team alignment
  • Quick problem-solving
  • Building teamwork

Core Concepts

1. Standard 3 Questions

  1. What did I complete yesterday?
  2. What will I work on today?
  3. What blockers do I have?

2. Standup Format

Time: 15 minutes (time-boxed) When: Same time daily Who: Development team + Scrum Master (+ PO optional) Where: Same location (physical or virtual)

Structure:

  • Walk the board (task-focused)
  • Round-robin (person-focused)
  • Today's plan first (future-focused)

3. Walking the Board

## Sprint Board Review

**To Do** → **In Progress** → **Done**

Story: User Login
├── Design mockup ✅ (Done)
├── API development 🔄 (Bob, blocked by auth library)
└── UI implementation 📋 (Alice, starting today)

Story: Password Reset
├── Email template ✅ (Done)
└── Backend logic 🔄 (Carol, testing today)

Best Practices

  1. Stand up - Literally stand (keeps it short)
  2. Time-box strictly - 15 minutes maximum
  3. Focus on sprint goal - Relevant updates only
  4. Identify blockers - Resolve offline
  5. Same time, same place - Consistency
  6. Everyone participates - No observers
  7. Update taskboard - Real-time visibility
  8. Park discussions - Take detailed talks offline

Resources

  • Standup Patterns: Effective formats
  • Virtual Standup Tools: Miro, Jira boards