The latest articles on DEV Community by Saroj Shrestha (@saroj_shrestha_dceb4ee0ac). https://dev.to/saroj_shrestha_dceb4ee0ac https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4155083%2F57a4d9d4-ef83-416a-bcac-aa58a253ad9c.png https://dev.to/saroj_shrestha_dceb4ee0ac en Saroj Shrestha Thu, 01 Oct 2026 14:33:05 +0000 https://dev.to/saroj_shrestha_dceb4ee0ac/how-to-run-planning-poker-with-a-remote-team-a-practical-guide-1ij5 https://dev.to/saroj_shrestha_dceb4ee0ac/how-to-run-planning-poker-with-a-remote-team-a-practical-guide-1ij5 <h1> How to Run Planning Poker With a Remote Team: A Practical Guide </h1> <p>Planning poker was designed for a conference room — cards on a table, everyone flipping at once. Remote teams can run it just as well, and in some ways better: digital tools eliminate the "I saw your card" problem entirely. Here's how to run planning poker with a distributed team, step by step.</p> <h2> What planning poker is (60-second refresher) </h2> <p>Planning poker is a consensus-based estimation technique. The team discusses a backlog item, then everyone privately selects an estimate (usually from a Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21), and all cards are revealed simultaneously. Big disagreements trigger discussion; the team re-votes until estimates converge. The simultaneous reveal is the whole point — it prevents anchoring, where the first or loudest voice drags everyone else along.</p> <h2> What you need before the session </h2> <ul> <li>A prioritized backlog with items refined enough to estimate</li> <li>A shared estimation tool — a free online planning poker room everyone can join from a browser, no signup ideally</li> <li>A video call running alongside for discussion</li> <li>A deck agreement: Fibonacci for story points, or t-shirt sizes (XS–XL) for rougher sizing</li> <li>A timebox: 60–90 minutes max</li> </ul> <h2> Running the session: step by step </h2> <p><strong>1. Set up the room (5 min).</strong> Create the planning poker room and share the link in the meeting chat. Do a practice vote on something silly to check the mechanics.</p> <p><strong>2. Present the item (2–3 min).</strong> The product owner presents one backlog item: what it is, why it matters, constraints. Keep it tight.</p> <p><strong>3. Clarifying questions (2–3 min).</strong> Timebox strictly. If it needs more clarification, it's not ready — park it.</p> <p><strong>4. Vote silently and simultaneously.</strong> Everyone selects privately, facilitator reveals all at once. No "I'm thinking it's a 5" before the reveal.</p> <p><strong>5. Discuss the outliers (3–5 min).</strong> Ask the highest and lowest estimators to explain briefly. The low voter often knows a shortcut; the high voter sees a hidden risk.</p> <p><strong>6. Re-vote until convergence.</strong> Usually 2–3 rounds. If not, the item is genuinely uncertain — take the higher estimate or split it.</p> <p><strong>7. Record and move on.</strong> About 5–8 minutes per item keeps energy up.</p> <h2> Remote-specific tips </h2> <ul> <li>Cameras on for discussion; use chat for "+1" instead of ten people unmuting.</li> <li>Name a facilitator, not the loudest engineer — and rotate the role.</li> <li>Mind time zones: schedule in the overlap window, keep sessions under 90 minutes.</li> <li>Async option for simple items: collect votes over a few hours, discuss only divergences live.</li> </ul> <h2> Common pitfalls </h2> <ul> <li>Anchoring: enforce simultaneous reveal, no discussion before voting.</li> <li>Senior dev dominates: ask juniors to explain first.</li> <li>Hours instead of points: agree upfront that points measure relative complexity.</li> <li>Endless discussion: 3-round limit, then higher estimate or split.</li> <li>Estimating unready items: park it — poker is for estimation, not refinement.</li> </ul> <h2> FAQ </h2> <p><strong>How many items per session?</strong> 8–12 in 60–90 minutes.<br> <strong>What if the team never agrees?</strong> After 2–3 rounds, take the higher estimate or split the item.<br> <strong>Should the product owner vote?</strong> Generally no — the PO presents the "what," the team estimates.<br> <strong>Can it work asynchronously?</strong> Yes for well-understood items; keep the hard ones synchronous.<br> <strong>What's a good free tool?</strong> Happy Backlog (<a href="https://happybacklog.com" rel="noopener noreferrer">https://happybacklog.com</a>) offers free planning poker with no signup — plus 13 more Scrum Master tools (retro templates, standup generator, team roulette, sprint calculators).</p> agile scrum remotework productivity