Step-by-step tutorial
How to run an asynchronous Scrum Poker session
Use this walkthrough for a complete estimation round, from the first ticket import to final CSV export and cleanup.
Start the tutorial in the appCreate the planning session
Open Create session, enter a session name and an optional team name. Use a name that people will recognize when they return later.
Choose the estimation scale
Keep the default 0, 1, 2, 3, 5, 8, 13, 21 scale or enter another ascending, comma-separated numeric scale used by your team.
Import and validate tickets
Choose Pasted list, Ticket links, or Excel / CSV. Review every row marked Ready and resolve duplicates or validation messages before continuing.
Create the session and save the private link
Select Create planning session once. Copy the Scrum Master link to a trusted private location; it is the credential for managing this session.
Share only the participant link
Send the participant link only to intended estimators; anyone holding it can read that session's ticket details and attempt to join. Never share the more powerful Scrum Master link, place either link in a public issue, or open either through an untrusted link-preview service.
Join and estimate
Each person enters a unique display name, then selects one value or Not part for every ticket. Estimates can be changed until reveal.
Monitor completion
The Scrum Master view shows who has completed the tickets without exposing hidden values. Refresh safely as people vote, and mark a participant inactive only when appropriate.
Reveal and review
Reveal when the team is ready. Compare estimates, review highlighted differences, and set the Final SP value for each ticket.
Export and delete
Export the final CSV for your work tracker. Delete the session when it is no longer needed, then confirm that the old role links no longer open it.
How to read the result
- Green: all included numeric estimates are the same.
- Yellow: estimates differ, but every value is within one position of the reference value on the configured scale.
- Red: at least one estimate is two or more scale positions away from the reference value.
The suggested SP is the configured scale value nearest to the numeric average. The Scrum Master can record a different Final SP after the team reviews the result.