Effective Daily Standups | Blocker-Focused
Run daily standups that provide value without wasting time. Focus on blockers and coordination, not status reports. Keep meetings under 15 minutes.
6 min read
Daily standups are the most common agile ceremony and the most frequently misused. Done poorly, they're boring status reports. Done well, they're focused coordination sessions that unblock the team and align priorities.
Standup Problems
| Bad Standup | Good Standup |
|---|---|
| Status reporting | Blocker focus |
| 30+ minutes | 15 minutes max |
| Everyone talks | Only relevant info |
| Passive listening | Active coordination |
| Late start, late end | On time, every time |
Effective Standup Format
Focused Agenda
EFFECTIVE STANDUP FORMAT
════════════════════════
TRADITIONAL (but often wasteful):
├── What did you do yesterday?
├── What will you do today?
└── Any blockers?
BETTER FORMAT:
─────────────────────────────────────
1. BLOCKERS (3 min)
"Who is blocked and needs help today?"
├── Surface immediately
├── Assign helper or take offline
└── Don't solve in standup
2. ANNOUNCEMENTS (2 min)
"What does everyone need to know?"
├── Priority changes
├── External dependencies
├── Important updates
└── Not status reports
3. BOARD WALK (10 min)
Walk the board right to left
├── Start with "almost done"
├── Focus on finishing
├── Identify stuck items
└── Skip items that are flowing
TOTAL: 15 minutes MAX
Board Walk Technique
BOARD WALK STANDUP
══════════════════
WALK RIGHT TO LEFT:
┌────────────────────────────────────────────────────────┐
│ Ready │ In Progress │ Review │ Done │
├────────────────────────────────────────────────────────┤
│ │ │ ← START HERE │
│ [Task] │ [Task] │ [Task] │ │
│ [Task] │ [Task] │ │ │
│ │ ← Then here│ │ │
└────────────────────────────────────────────────────────┘
FOR EACH ITEM:
├── "Is this blocked?"
├── "What's needed to finish?"
├── "Who can help?"
└── Skip if flowing normally
WHY RIGHT TO LEFT:
├── Finish work before starting new
├── Focus on items closest to done
├── Identify stuck items quickly
└── Reduce WIP naturally
EXAMPLE:
"GS-234 is in Review for 2 days. Mike, can you
review today? Sarah will be available to help."
SKIP:
"GS-235 is progressing fine" - just move on
Async Standups
Written Updates
ASYNC STANDUP FORMAT
════════════════════
WHEN TO USE:
├── Distributed team (timezone gaps)
├── Focus time priority
├── Team is self-directed
├── Low coordination needs
└── Status visibility sufficient
TEMPLATE (post by 10am local):
─────────────────────────────────────
**Yesterday**: Completed GS-234 login API
**Today**: Starting GS-235 password reset
**Blocked**: None
─────────────────────────────────────
WHERE:
├── #team-standup Slack channel
├── GitScrum daily update feature
├── Shared document
└── Dedicated standup tool
RESPONSE EXPECTATIONS:
├── Post by 10am
├── Read others' updates
├── Respond to blockers
├── No lengthy discussion (take to thread)
SYNC IF NEEDED:
├── If blocker can't resolve async
├── If complex coordination needed
├── Weekly sync for alignment
└── Not by default
Hybrid Approach
HYBRID STANDUP MODEL
════════════════════
MONDAY/FRIDAY: Sync standup
├── Week kickoff alignment
├── Week wrap-up / retrospective
├── Face time for culture
└── 15 min max
TUESDAY-THURSDAY: Async
├── Written updates by 10am
├── Focus time protected
├── Board review individual
└── Sync if blocked
BENEFITS:
├── Minimal meetings (2/week)
├── Maximum focus time
├── Maintains team connection
├── Timezone friendly
└── Scales well
RULES:
├── Sync days are mandatory
├── Async days have deadline
├── Blockers trigger sync
├── Manager monitors for issues
Running Effective Standups
Facilitation Tips
STANDUP FACILITATION
════════════════════
START ON TIME:
├── Don't wait for latecomers
├── Start exactly at scheduled time
├── Latecomers catch up after
└── Respect those who are on time
KEEP MOVING:
├── 30-60 seconds per person max
├── "Take it offline" for discussions
├── Park detailed topics
├── Use timer if needed
FOCUS ON BLOCKERS:
├── "Anyone blocked?"
├── "What needs attention?"
├── Less "what I did" more "what I need"
└── Action-oriented
VISUALIZE:
├── Look at the board, not people
├── Point to specific items
├── Update board during standup
└── Everyone can see status
END ON TIME:
├── Hard stop at 15 minutes
├── Take remaining topics offline
├── Protect team's time
└── Builds trust in process
Common Problems
STANDUP ANTI-PATTERNS
═════════════════════
PROBLEM: Too long (30+ min)
SOLUTION:
├── Strict 15-min timer
├── Take discussions offline
├── Reduce team size (split)
└── Use board walk, not round-robin
PROBLEM: Status reporting theater
SOLUTION:
├── Change format to blockers-first
├── Skip items flowing normally
├── Ask "do you need anything?"
└── Trust the board for status
PROBLEM: Late start, waiting
SOLUTION:
├── Start on time, always
├── Latecomers catch up themselves
├── Track patterns, address individually
└── Cultural expectation of punctuality
PROBLEM: Sidebar conversations
SOLUTION:
├── "Let's take this offline"
├── Facilitator enforces
├── Park lot for topics
└── Follow up after standup
PROBLEM: Not everyone speaks
SOLUTION:
├── Round-robin only if needed
├── Ask directly: "Maria, any blockers?"
├── Make it safe to say "all good"
└── Check in 1:1 if persistent
GitScrum Standup Support
Board During Standup
USING GITSCRUM IN STANDUP
═════════════════════════
BEFORE STANDUP:
├── Open team board
├── Review items in progress
├── Note aged items
├── Identify blockers
DURING STANDUP:
├── Share screen with board
├── Walk columns right to left
├── Update blockers in real-time
├── Assign items as discussed
AFTER STANDUP:
├── Async updates posted
├── Blocker labels added
├── Follow-up actions created
└── Board reflects reality
HELPFUL VIEWS:
├── Filter: Assigned to team
├── Sort: By status, age
├── Highlight: Blocked items
└── Show: WIP per person
Best Practices
For Standups
Anti-Patterns
STANDUP MISTAKES:
✗ Lengthy status reports
✗ Problem-solving in standup
✗ Waiting for latecomers
✗ No visual board
✗ Manager interrogation
✗ Skipping when busy
✗ Round-robin when unnecessary
✗ Running over time