ShakaShuffle

Why I made it

Planning poker does not need to feel like admin

Planning poker is useful because everyone chooses an estimate before the group starts debating it. The interesting part is the discussion when the cards do not match, not setting up another complicated meeting tool.

I made ShakaShuffle to keep that process quick and make it a bit more fun. The quokka and shaka theme is there because sprint planning could use something less serious in the room.

How it works

Pick a card, reveal together, talk about the gaps

A facilitator adds the tasks and controls when the cards are revealed. Everyone votes without seeing the other estimates first. After the reveal, the table shows the spread and whether the team reached consensus.

Teams can keep a squad, invite people with a code and run one active session together. There is enough structure to use it every sprint without setting everything up again.

• Realtime voting across distributed teams
• Facilitator-controlled reveal to limit anchoring bias
• Consensus feedback that makes disagreement visible
• Reusable squads, member roles, and invite flows

What I built

A simple table with a lot happening underneath

The main technical problem is keeping joins, votes, reveals and task changes in sync for everyone at the table. Those updates need to arrive in the right order or the meeting gets confusing quickly.

I use Supabase Realtime for the live updates, with server-side checks around the important actions. The interface tries to keep all of that out of sight and just make the cards feel immediate.