What is "story points" in Agile? Please what do story points represent? Are they a…
- User
What is "story points" in Agile? Please what do story points represent? Are they a measure of time, what is the purpose of using story points for estimation, and what is "planning poker".
- Assistant
Hmm, the user is asking about story points in Agile, covering multiple aspects: definition, what they represent, whether they measure time, purpose of using them, and planning poker. This is a structured question, so the response should be equally organized.
First, I need to clarify that story points are not a time measure but a relative complexity measure. The user might be confusing them with hours or days, so I should emphasize the comparative nature—like comparing sizes of fruits instead of weighing them.
Next, the purpose: why use story points instead of time? Key points are team calibration, abstraction from time (avoiding false precision), and incorporating uncertainty. The user might benefit from knowing common pitfalls (like management misusing them as time metrics).
Planning poker is a specific technique, so I should explain the process briefly—cards, discussion, consensus—and why it works (collaboration, avoiding anchoring). The Fibonacci sequence detail matters here because it reflects increasing uncertainty.
The user’s tone is neutral but inquisitive, likely someone learning Agile or preparing for a Scrum role. I’ll keep it practical, avoid jargon overload, and include concrete examples (like the coffee mug vs. bicycle analogy). Also, I should warn about common misuse since that’s a real-world issue.
Structure: start with a clear definition, then breakdown each sub-question in order. End with a summary table for quick reference—users often appreciate that. No need for fluff; just crisp explanations. Excellent questions. Let's break down story points, a core but often misunderstood concept in Agile (specifically Scrum).
1. What are Story Points?
Story points are a unit of measure for estimating the relative effort (or complexity, risk, and uncertainty) required to complete a Product Backlog Item (PBI), typically a user story.
They are not a measure of time. They are a sizing tool.
2. What Do Story Points Represent?
Story points represent a combination of:
- Effort: The amount of work to be done.
- Complexity: How technically difficult or intricate the work is.
- Risk: The amount of uncertainty or unknowns (e.g., new technology, ambiguous requirements).
- Amount of Work: Sometimes loosely tied to volume, like lines of code or number of screens.
Crucially: They are relative to other stories, not absolute. Your team doesn't say "this story is 5 points because it takes 5 hours." Instead, you say "This story feels about twice as complex/uncertain/large as that baseline '3-point' story we did last week."
Common Analogy: Estimating fruits.
- A grape = 1 point (trivial, known, tiny effort).
- An orange = 2 or 3 points (small but more work than a grape).
- A watermelon = 8 points (big, complex, requires planning and multiple people). You're comparing sizes, not weighing each fruit in grams.
3. Are They a Measure of Time? (The #1 Misconception)
No. This is critical. Story points are not person-hours, person-days, or any other unit of time.
- Why not use time? Time is highly variable between teams and individuals. A "5-hour task" for a senior developer might take a junior 15 hours. Time estimates are also often false precision ("I think it will take exactly 3.5 days").
- What's the point of decoupling from time? It forces the team to think about size and complexity first. Once you have a stable velocity (average points completed per sprint), you can forecast how much work you can take, but the estimate itself remains a measure of size.
Example: Team A completes 30 points per sprint. A 5-point story might take 1 day for them. Team B, with different skills, might complete 50 points per sprint. The same 5-point story for Team B might also take 1 day. The points stayed the same, but the time output per point differs. This is why you never compare velocities between teams.
4. Purpose of Using Story Points for Estimation
The main goals are:
- Team Calibration & Shared Understanding: The discussion to assign points (
"Why do you think this is an 8 and I think it's a 5?") is often more valuable than the number itself. It surfaces assumptions, risks, and requirements. - Forecasting & Capacity Planning: By tracking how many points a team completes per sprint (Velocity), they can predict how much work they can likely take in future sprints. It's a historical measure of capacity, not a target.
- Abstraction from Time: Avoids the pressure and inaccuracy of "when will it be done?" tied directly to hours/days.
- Incorporating Uncertainty: Larger, more complex stories naturally get more points, reflecting their higher risk and unknown effort.
- Focus on Value Delivery: The goal becomes "deliver more points of valuable, done work" rather than "work more hours."
5. What is "Planning Poker"?
Planning Poker is a consensus-based, gamified estimation technique commonly used to assign story points. It's designed to be engaging and surface different viewpoints.
How it works:
- The Product Owner presents a user story and clarifies requirements.
- The team discusses the story, asking questions to understand scope and complexity.
- Each team member (including the PO and Scrum Master, if they are doing the work) privately selects a card from a deck (usually using the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 20, 40, 100, and ? for "too big/unknown").
- Everyone reveals their cards simultaneously.
- Key Step: If estimates differ significantly (e.g., one person says 3, another says 8), the high and low estimators explain their reasoning. This discussion often reveals hidden complexities, assumptions, or risks.
- The team re-votes. They repeat discussion and voting until they converge on a single estimate (or decide the story is too big and needs splitting). The estimate is the team's, not an average.
Why it's effective:
- Prevents anchoring bias (where the first spoken number influences others).
- Ensures every voice is heard, especially quiet team members.
- Turns estimation into a collaborative problem-solving session.
- Uses the Fibonacci sequence intentionally—the gaps increase to reflect the growing uncertainty and non-linearity of effort for larger stories (an 8-point story isn't just 2x a 4-point story; it's much more uncertain and complex).
Summary Table
Concept What It Is What It Is NOT Story Points A unit of relative effort/complexity/risk. A unit of time (hours, days). Purpose Team calibration, forecasting via velocity, abstraction from time. A performance metric for management, a personal commitment. Planning Poker A collaborative estimation technique to achieve team consensus. A tool for management to assign blame or set deadlines. Final Golden Rule: Story points are for the development team, by the development team. They are a tool for their planning and process improvement. When managers or Product Owners start asking "why is this 8 points instead of 5?" or compare velocities between teams, the system is being misused. The real value is in the conversation, not the number.