Consensus Fatigue in Scrum: Combat Groupthink in Planning Poker
After 90 minutes of refinement, team agrees on story #18 not because they're aligned, but because they want the meeting to end. Consensus fatigue creates false agreement. Here's how to combat groupthink.
Signs of Groupthink
- Votes converge faster in second half of session
- "Whatever, let's just go with 5" comments increase
- Outlier votes disappear (everyone votes middle)
- Less discussion per story as time passes
- Private Slack messages: "I didn't agree but was tired"
Why Long Sessions Create Groupthink
Groupthink psychology: Desire for harmony overrides critical thinking. In tired teams, "just agree" becomes easier than "challenge assumption."
Prevention Techniques
1. Hard 60-Minute Time Limit
Never run refinement past 60 minutes. If stories remain, schedule second session next day. Fatigue kills quality.
2. Anonymous Voting
Hide voter names on first reveal. Removes social pressure to conform with majority/senior engineers.
3. Devil's Advocate Role
Rotating role: "Your job this story is to challenge the consensus vote." Forces critical thinking.
4. Confidence Voting After Estimate
After agreeing on 5 points, vote confidence: 🟢 High / 🟡 Medium / 🔴 Low. If multiple reds, discussion wasn't complete.
5. Break After 30 Minutes
5-minute break mid-session resets cognitive fatigue. Prevents late-session groupthink.
Red Flags: Stop and Reschedule
- More than 2 "let's just move on" comments
- Zero outlier votes for 5+ consecutive stories
- Discussion time per story dropping below 2 minutes
- Team energy visibly low (camera-off, muted throughout)