Agile & Scrum Guides
In-depth guides to Scrum Poker, story points, and agile estimation technique, written to answer the real questions teams run into, not to rank for a keyword. Looking for a calculator instead? See free tools.
Story Points
Story Points: The Complete Guide to Agile Estimation Units
What story points are, what they measure, and how agile teams use them well, including the Fibonacci scale, baselines, velocity, and the mistakes that make points meaningless.
Read guide →Fibonacci Story Points: Why the Gaps Get Wider
Why Fibonacci is the default story point scale, why the gaps between numbers widen on purpose, the variants you'll see in different tools, and the most common mistakes teams make with it.
Read guide →Story Point Cheat Sheet
A dense, one-page reference: the Fibonacci scale, baseline examples per size, the rules compressed, conversion anti-patterns to avoid, and quick velocity math.
Read guide →Story Point Estimation Examples: 12 Worked Stories
Twelve realistic backlog items (features, bugs, and technical work) each sized on Fibonacci and t-shirt scales with the reasoning a real team would use.
Read guide →
Scrum Poker
Scrum Poker: The Complete Guide
What Scrum Poker is, how a round actually works, the real rules, who should vote, and why hidden votes are the whole point, plus its history and how it compares to other estimation techniques.
Read guide →Scrum Poker Facilitator One-Pager
A printable, condensed facilitation script for running a Scrum Poker session round by round: before, during, and after, distilled from the complete Scrum Poker guide.
Read guide →Scrum Poker Rules: The Complete Reference
Every Scrum Poker rule in one place: who votes, what the cards mean, who reveals, what happens on a tie, and the edge cases that trip up a team's first few sessions.
Read guide →Scrum Poker Example Session: 5 Stories, Start to Finish
A full worked Scrum Poker session, four developers, five real stories, disagreements and all, ending with the exported round history.
Read guide →The Remote Team's Guide to Scrum Poker
What breaks when Scrum Poker moves from a room to a video call, and the specific practices (pre-reading, visible timers, async voting across time zones) that keep remote estimation tight.
Read guide →
Agile Estimation
Agile Estimation Techniques: A Complete Guide
A full comparison of agile estimation techniques (Scrum Poker, t-shirt sizing, affinity estimation, the bucket system, dot voting, Wideband Delphi, and three-point estimation) with guidance on which fits your team and when.
Read guide →Agile Estimation Techniques: Comparison Matrix
A printable one-page matrix comparing every major agile estimation technique: what it optimizes for, team size, whether it feeds velocity, and when to use it, condensed from the full agile estimation guide.
Read guide →T-Shirt Sizing for Agile Estimation
How t-shirt sizing (XS-XXL) trades precision for speed, when it beats Scrum Poker, and the real limitation: t-shirt sizes don't sum into a velocity number without a mapping.
Read guide →Three-Point (PERT) Estimation
How three-point estimation combines optimistic, most likely, and pessimistic values into a weighted expected value with a confidence range: the (O + 4M + P) / 6 formula, when to use it, and when not to.
Read guide →Relative Estimation: The Idea Behind Every Agile Technique
Why comparing work to other work beats predicting absolute duration: the human-limitation research behind it, and a worked door/house example that needs no software background.
Read guide →Affinity Estimation: Sizing a Large Backlog Fast
How silently sorting backlog items along a size spectrum sizes dozens of items in minutes: the mechanism, a worked 80-item example, and what the speed costs you.
Read guide →The Bucket System: Estimating Very Large Backlogs
A more structured, more parallelizable version of affinity estimation for portfolios with hundreds of items: how it works, a worked 300-item example, and when the extra structure earns its keep.
Read guide →Wideband Delphi: The Root of Scrum Poker
How the Delphi forecasting method (RAND Corporation, 1950s) became Barry Boehm's software cost-estimation technique, and why its independent-judgment-then-discussion structure is the direct ancestor of Scrum Poker.
Read guide →Dot Voting: Prioritization, Not Estimation
Why dot voting answers "what matters most," not "how big is this": how the technique works, where it genuinely fits, and the common mistake of using it as an estimation shortcut.
Read guide →