
I Built My Own Scrum Poker Because All Others Suck π΄
The Problem π© Sprint planning. Your team needs to estimate tasks. Someone shares a Planning Poker link. You click. You wait. Half the team can't connect. The other half already went for coffee. Sound familiar? At AGG TEAM , we tried everything: Planning Poker Online (laggy, ads, ancient UI) Scrum Poker for Jira (expensive, requires Jira) PlanITpoker (works, but missing OUR features) After the third crash mid-estimation, I thought: "Screw it, I'll build my own." The Real Challenge: 6 Teams, 1 Room π€― Here's the twist: we don't have ONE scrum team. We have SIX departments : Frontend, Backend, DevOps, QA, Analytics, Management Everyone wants to do planning poker. Simultaneously. In one room. It's chaos. Like playing six different card games at the same table. Existing tools say: "Here's one room, figure it out!" Not ideal. What I Built π° Multi-Table Support (Up to 6!) Core concept: one session, multiple independent tables. interface Table { id : string ; name : string ; // "Frontend Squad"
Continue reading on Dev.to Webdev
Opens in a new tab



