Planning Poker Guides
Practical resources to run better estimation sessions with your agile team — from the basics of Planning Poker to importing your Jira sprint into a live session.
What is Planning Poker? A Practical Guide for Agile Teams
How the estimation game works, the rules, the card scales, common mistakes and how to run a session with a remote team.
Fibonacci vs T-Shirt Sizing: Which Estimation Scale to Use
How each scale works, when to pick one over the other, conversion tips and how to avoid false precision.
How to Run Planning Poker with Jira (Step-by-Step)
Connect Jira, import your active sprint into a task playlist, estimate each issue in order and write points back to your board.
9 Planning Poker Mistakes That Wreck Your Estimates
Anchoring, averaging votes, silent seniors, endless debates and eight-point stories that should be split — with the fix for each.
How to Run Planning Poker with a Remote or Hybrid Team
An agenda that fits 45 minutes, hybrid-room pitfalls, async voting across time zones and how to keep quiet participants involved.
Story Points vs Hours: Which Should Your Team Estimate In?
Where each unit works, how to answer "when will it be done?" without converting points to days, and how to migrate between them.
Team Velocity: How to Measure It and What It Cannot Tell You
How to calculate velocity, forecast with a range instead of an average, and diagnose a number that suddenly moves.
Backlog Refinement: Running a Session That Produces Estimable Stories
A definition of ready you can apply, six ways to split oversized stories, and an agenda that fits one hour.
Facilitating Your First Planning Poker Session: A Complete Walkthrough
How to prepare the backlog, set the rules, handle the first estimate and manage loud voices — so the first session earns the team's trust.
How to Split Large User Stories: 8 Patterns That Actually Work
Vertical slicing by workflow step, business rule, data variant and more — turning 20-point guesses into estimable, deliverable stories.
Should You Estimate Bugs and Technical Debt? A Practical Framework
When to estimate bugs and debt in points, when to time-box instead, and how to keep your velocity forecast honest.