Blog
Agile estimation tips and sprint planning guides.
5 Common Planning Poker Mistakes (And How to Fix Them)
Planning poker only works when the team trusts the numbers. These five mistakes quietly undermine that trust - and the fixes are simpler than you think.
35 more articles
ProcessEstimation Anti-Patterns That Kill Sprint Velocity
Some estimation habits feel productive but consistently produce worse results. Here are the most common anti-patterns and how to eliminate them from your planning process.
Team DynamicsHow Team Size Affects Your Estimation Accuracy
Small teams and large teams estimate differently - and each has predictable failure modes. Here's how to get reliable estimates regardless of how many people are in the room.
ProcessWhen to Re-Estimate Mid-Sprint
Scope changes during a sprint. Most teams ignore it. Here's when re-estimating in the middle of a sprint improves delivery and when it just creates churn.
ProcessSprint Zero: What to Estimate Before You Even Start
Sprint Zero is setup time before delivery begins. Estimating it well sets the whole project up for reliable planning. Here's what belongs in Sprint Zero and how to size it.
FundamentalsHow to Estimate Bug Fixes in Your Backlog
Bug fixes are notoriously hard to estimate because the scope is often unknown until you're in the code. Here's a framework for sizing them without wild guessing.
Team DynamicsThe Danger of Anchoring in Agile Estimation
Anchoring is the most common and least-discussed problem in planning poker. The first number a team hears shapes every vote that follows. Here's how to prevent it.
Team DynamicsMob Estimation: When the Whole Team Votes at Once
Mob estimation runs planning poker with the entire team in the same room, all voting simultaneously. For some teams, it's faster and more accurate than standard sessions.
ProcessHow to Use Historical Velocity for Better Sprint Planning
Velocity only becomes useful after you have enough data. Here's how to use your team's history to make sprint commitments that actually stick.
FundamentalsSplitting User Stories Without Losing Estimation Value
Splitting stories to fit a sprint is easy. Splitting them so the pieces remain independently deliverable and estimable is harder. Here's how to do it right.