Planning guide
Asynchronous Scrum Poker guide
Prepare a useful ticket list, collect independent estimates without a meeting, and reveal the result when the team is ready.
1. Prepare the session
Give the session a recognizable name and, if useful, a team name. Start with the default numeric scale of 0, 1, 2, 3, 5, 8, 13, 21, or enter another ascending scale that your team already understands.
Keep each ticket focused enough to estimate. A short title is required; an external ticket ID, valid HTTP or HTTPS URL, description, priority, and notes are optional. The app checks URL syntax and protocol, not the reputation or safety of the destination.
2. Import and validate tickets
Paste a list, paste ticket links, or upload a CSV, XLS, or XLSX workbook. Files are limited to 2 MiB, and a session can contain up to 200 tickets.
Review the preview before creating the session. Fix malformed rows, unsafe links, and duplicate tickets while they are still visible. The original workbook is not stored; only the normalized ticket rows used for the session are submitted.
Open the import preview4. Vote asynchronously
Each participant joins with a unique display name and estimates every ticket. Other people can see completion status, but the server does not return their estimate values before reveal. Select Not part when a ticket is outside your area; it counts as completed but is excluded from averages and consensus calculations.
The browser keeps one participant session credential at a time. Returning to the most recently joined session in the same browser can restore that identity. Joining another session, clearing site data, or switching browsers can prevent restore. The old display name may remain reserved. Use another unique display name; the Scrum Master can mark the old identity inactive so it does not block completion.
5. Reveal, discuss, and record the result
The Scrum Master can monitor completion and mark someone inactive when they are no longer participating. Revealing with incomplete active participants requires an explicit warning confirmation. Reveal locks participant voting.
Results show the average, a suggested value from the configured scale, a consensus color, and highlighted outliers. The Scrum Master can set the final story point and export the results as CSV.
6. Protect and finish the session
Do not place passwords, access tokens, customer secrets, or other unnecessary sensitive data in ticket text. Delete the session when the results are no longer needed; deletion invalidates both role links. Active sessions expire after 30 days by default.
Need a shorter walkthrough? Read the step-by-step tutorial, or check the FAQ for common questions.