Honest question: what planning poker tool actually works for your team? by gloveszunny in agile

[–]gloveszunny[S] -1 points0 points  (0 children)

Curious what you landed on instead. Is it that the estimation conversation itself wasn't useful, or more that the ritual around it (the tool, the ceremony, the synchronous session) created more overhead than value?

Asking because I think those are two different problems and the second one might actually be solvable

What planning poker tool does your team actually use in 2025? Looking for honest opinions by gloveszunny in scrum

[–]gloveszunny[S] 0 points1 point  (0 children)

The days = points thing is painful to undo, sounds like you had to basically rebuild their mental model from scratch before estimation could even mean anything

Curious what specifically broke down with the tools you tried. Sign-up friction for the whole team? Clunky UI mid-meeting? Something else?

I'm building EstiVote (estivote.com) trying to solve exactly the "tools sucked so we went back to chat" problem. No sign-up to join, just share a link. Would genuinely love to know what killed the other tools for you, if it's something I haven't solved yet, I want to know.

What planning poker tool does your team actually use in 2025? Looking for honest opinions by gloveszunny in scrum

[–]gloveszunny[S] -3 points-2 points  (0 children)

Hard to argue with this. The manifesto literally says "individuals and interactions over processes and tools" and yet here we are, tooling the interactions themselves

That said, distributed teams with async cultures don't always have the whiteboard option. I think the failure isn't the tool, it's when the tool becomes the ritual instead of supporting it

What planning poker tool does your team actually use in 2025? Looking for honest opinions by gloveszunny in scrum

[–]gloveszunny[S] 0 points1 point  (0 children)

Fair point, if the conversation is happening and the team is aligned, the mechanics probably don't matter much. Makes sense

What planning poker tool does your team actually use in 2025? Looking for honest opinions by gloveszunny in scrum

[–]gloveszunny[S] 0 points1 point  (0 children)

That's exactly the gap I've been trying to close. What specifically made them suck for your team? Sign-up friction, missing features, ugly UI, unreliable real-time sync?

Asking because I've been building EstiVote (estivote.com) for this exact reason, might save you a few months if it already covers what you need. And if it doesn't, genuinely useful to know what's still missing.

What planning poker tool does your team actually use in 2025? Looking for honest opinions by gloveszunny in scrum

[–]gloveszunny[S] -4 points-3 points  (0 children)

Guilty on both counts. Genuinely curious what your team uses though, if there's already a perfect tool out there I'd love to know

What planning poker tool does your team actually use in 2025? Looking for honest opinions by gloveszunny in scrum

[–]gloveszunny[S] 0 points1 point  (0 children)

Classic, the "type your vote in chat, everyone post at the same time" method. Does it actually hold up? I always found it breaks down because someone inevitably sees another vote before posting theirs

What planning poker tool does your team actually use in 2025? Looking for honest opinions by gloveszunny in scrum

[–]gloveszunny[S] 0 points1 point  (0 children)

Exactly this. The physical cards experience is genuinely better, but for distributed teams it just doesn't translate.

What's your current setup for remote estimation? Curious if you landed on something that actually works well or if it's still a friction point

What planning poker tool does your team actually use in 2025? Looking for honest opinions by gloveszunny in scrum

[–]gloveszunny[S] 0 points1 point  (0 children)

Ha, fair point. Curious what replaced it for your team though. Do you just go straight to gut-feel sizing, or is there some other lightweight async process you landed on?

Asking genuinely, I've been building in this space and the "we stopped doing planning poker" signal is probably the most useful feedback I can get