Planning Poker Template
Bug Triage
Classify bugs by severity before they hit production
Use planning poker to reach team consensus on bug severity — Low, Medium, High, or Critical. Silent voting prevents the loudest voice from dominating. Engineers who found the bug, QA, and product all vote together, so severity decisions reflect real business impact rather than individual opinion. Reduces revisits and mis-prioritization in the backlog.
Deck type
risk
Duration
30 minutes
Team size
3–8 people
Estimation focus
Severity and business impact
Steps
- 01Pull open bug reports into the session queue
- 02Read the reproduction steps aloud or share the screen
- 03Vote on severity — Low, Medium, High, or Critical
- 04Reveal and discuss any splits in the vote
- 05Assign the agreed severity and set the fix priority
- 06Move to the next bug
When to use
Weekly or after a major release when the bug backlog grows. Works best when both engineering and product are present to weigh customer impact.
Related templates
Open this template in a room
Create a free Plandeck room pre-configured with this template. No signup required.