Planning Poker for Non-Technical Team: Explain Story Points to Product Managers
Product manager joins estimation, sees Fibonacci sequence (1, 2, 3, 5, 8, 13), asks "What's a 5?" Engineers give technical explanation that confuses more than clarifies. Here's how to include non-technical stakeholders.
Why Non-Technical Voters Struggle
- Fibonacci is abstract: No intuitive meaning
- Technical complexity discussions: "API endpoints" means nothing to PM
- Impostor syndrome: Afraid to vote "wrong"
- Different baseline: PM thinks in business value, devs in technical complexity
Solutions for Mixed Technical Teams
1. Use T-Shirt Sizing
XS, S, M, L, XL more intuitive than Fibonacci. Everyone understands "this is a Large."
2. Provide Reference Stories
Show concrete examples:
- 3 points: "Like when we added password reset link"
- 5 points: "Similar to user profile page update"
- 8 points: "Complexity of OAuth integration"
3. Observer Role
PMs don't have to vote. "You're here to answer questions and learn, voting optional."
4. Business Complexity vs Technical Complexity
Explain: "You know business complexity. We're estimating technical complexity. Your input on requirements helps us estimate accurately."