Relative Sizing & Planning Poker: Agile Estimation Guide
Relative sizing estimates work by comparing it to reference stories, not hours. Learn planning poker step by step with a script and worked round.
Read article →Updated 2026-10-07
Agile Planning & Estimation Articles
Practical guides to planning poker, story points, velocity, and running better team meetings, with worked examples, templates, and scripts you can use in your next session.
Estimation and story points
Relative sizing, estimation scales, and how to size work consistently.
Story Points vs Hours: Why Not to Convert (and What to Do)
Story points measure relative size; hours measure time. Learn why converting story points to hours backfires and what to give management when they insist.
Read article →Updated 2026-10-07
Fibonacci vs T-Shirt Sizing: Agile Estimation Scales
Fibonacci suits sprint story points; T-shirt sizing suits roadmaps. Compare 5 estimation scales and copy a ready-made estimation scale reference card.
Read article →Updated 2026-10-07
Complexity vs Effort in Story Points: The 3-Factor Model
Story points combine complexity, effort, and uncertainty. Use this scoring rubric and three worked stories to stop estimation debates and spot risky work.
Read article →Updated 2026-10-07
How to Estimate Large Epics and Split User Stories
A 13-point story is usually too big. Learn 7 patterns to split user stories and epics, with a worked example splitting a 40-point epic into stories.
Read article →Updated 2026-10-07
Should Bugs Have Story Points? Estimating Tech Debt
Both sides of the story points for bugs debate, a decision table for bugs, tech debt and spikes, and a worked example of planning with segmented velocity.
Read article →Updated 2026-10-07
Calibrating Story Points: Fix Estimation Drift and Accuracy
How to calibrate story points: build a reference-story baseline, run a quarterly blind re-estimate, and measure accuracy with say/do and cycle-time spread.
Read article →Updated 2026-10-07
Reestimating Stories: Should You Re-Point Mid-Sprint?
Usually no: keep the estimate when work turns out harder. Re-estimate only for real scope change. Decision table and carry-over point rules inside.
Read article →Updated 2026-10-07
Standardize Story Points Across Teams (Without Breaking Them)
What to standardize across teams (scale, Done, references) and what not to, plus a balanced look at SAFe normalized story points and multi-team velocity.
Read article →Updated 2026-10-07
Confidence Voting: Fist of Five and Sprint Confidence
Confidence voting in Scrum explained: run a fist-of-five sprint confidence vote, what to do with 1s and 2s, and how per-estimate confidence weighting works.
Read article →Updated 2026-10-28
Running planning poker
Facilitation, group dynamics, and protecting honest estimates.
How to Facilitate Planning Poker: Agenda, Scripts, Timeboxes
How to run planning poker: a prep checklist, a minute-by-minute 60-minute agenda, timebox rules per story, and exact phrases for outliers and stalled debates.
Read article →Updated 2026-10-07
Anchor Bias in Planning Poker: Blind Voting and Fixes
Anchoring bias skews story points when one number is heard first. See the 9 most common anchor sources in planning poker, a fix for each, and blind voting rules.
Read article →Updated 2026-10-07
Consensus Fatigue & Groupthink in Planning Poker
How many rounds should planning poker take? Revote rules, when to take the higher estimate or split the story, and a high/low explainer protocol to beat groupthink.
Read article →Updated 2026-10-07
Management Pressure on Estimates: Scripts to Push Back
Manager wants lower story points? Negotiate scope, date, or confidence instead of the number. Word-for-word scripts plus a forecast-with-range method you can copy.
Read article →Updated 2026-10-07
Planning Poker for Non-Technical Team Members
How product managers, designers, and other non-developers can take part in planning poker: what to vote on, when to spectate, reference stories, and a jargon guide.
Read article →Updated 2026-10-07
Jira Planning Poker & Story Points: A Practical Guide
How story points work in Jira, how to configure estimation, and a copy-paste workflow to run planning poker in any tool and write points back to Jira.
Read article →Updated 2026-10-07
Velocity and sprint planning
Velocity, forecasting, sprint planning, and backlog refinement.
How to Calculate Team Velocity in Agile (Formula + Examples)
Velocity = story points completed per sprint, averaged over 3-6 sprints. See the formula, a worked 6-sprint example, capacity adjustments and Jira steps.
Read article →Updated 2026-10-07
Sprint Planning Best Practices: Agenda + Capacity Example
How to run sprint planning per the 2020 Scrum Guide: the why/what/how topics, a 2-hour agenda, a worked capacity example, and fixes for common mistakes.
Read article →Updated 2026-10-07
Definition of Ready Checklist and User Story Template
Copy-paste Definition of Ready checklist, lean user story template with Given/When/Then examples, INVEST explained, and when DoR becomes a harmful gate.
Read article →Updated 2026-10-07
How to Shorten Backlog Refinement: Batch Size + Fast Methods
Cut refinement to 45 minutes: how many stories per session, affinity estimation and the bucket system step by step, plus a reusable minute-by-minute agenda.
Read article →Updated 2026-10-07
Definition of Done: Examples vs. Acceptance Criteria
Definition of Done per the Scrum Guide, copy-ready DoD examples for web, data and non-software teams, and how it differs from DoR and acceptance criteria.
Read article →Updated 2026-10-07
Agile Workflow Optimization: WIP Limits and Flow Metrics
Optimize your Scrum team workflow with WIP limits, cycle time, and flow metrics. Includes a worked example, Little's Law, and a 3-sprint improvement plan.
Read article →Updated 2026-10-07
Scrum Master Role in 2026: Skills and Responsibilities
The Scrum Master role per the 2020 Scrum Guide: what they're accountable for, the skills that matter in 2026, a weekly routine, and anti-patterns to avoid.
Read article →Updated 2026-10-07
Remote teams and meetings
Async estimation, distributed teams, icebreakers, and meeting costs.
Async Planning Poker: Estimating Across Time Zones
How to run async planning poker across time zones: a 48-hour estimation cadence, overlap-window table, which stories to keep sync, and reminder templates.
Read article →Updated 2026-10-07
Offshore Team Story Pointing: Distributed Estimation Guide
How to include offshore teams in story pointing: fix time zones, language barriers, and hierarchy so the people who build the work help estimate it. Scripts inside.
Read article →Updated 2026-10-07
Remote Team Decision Making: Problems and Fixes
Why remote teams stall on decisions and how to fix it: consent, DACI, RAPID, and disagree-and-commit with a when-to-use table, async decision doc template, and scripts.
Read article →Updated 2026-10-07
Icebreakers That Don't Suck: 40 for Remote Teams
40 non-awkward icebreakers for work, grouped by time (1, 5, 15 min) and meeting type, plus facilitation tips and the icebreakers remote teams hate.
Read article →Updated 2026-10-07
Cost of Meetings: Formula, Calculator & How to Cut It
How much does a meeting cost? Use attendees x loaded hourly rate x hours, see a weekly status meeting annualized, and follow a playbook to cut the cost.
Read article →Updated 2026-10-07
Analyze Sprint Meeting Minutes with Claude: 8 Prompts
Paste planning poker minutes into Claude or another AI assistant to find estimation outliers, risks, and stories to split. 8 copy-paste prompts and a sample.
Read article →Updated 2026-10-07
AI Sprint Retrospectives: Prompts, Formats, and Limits
How to use Claude or another AI assistant in sprint retrospectives: 7 copy-paste prompts, which retro formats work best with AI, and where AI gets it wrong.
Read article →Updated 2026-10-07
Agile beyond software
Sprints and estimation for sales, finance, HR, marketing, and hardware teams.
Agile for Non-Software Teams: Finance, HR & Marketing
How to run agile in non-software teams: what transfers, what doesn't, plus sample sprint backlogs and done criteria for finance, HR, and marketing.
Read article →Updated 2026-10-07
Agile Sales Teams: Sales Sprints and Deal Qualification
How to run an agile sales team: 2-week sales sprints, revenue team alignment, and team deal-qualification voting with BANT, MEDDIC, CHAMP, or GPCT.
Read article →Updated 2026-10-07
Agile for Hardware: Lean and Agile Product Development
How hardware teams run agile despite lead times, tooling, and certification: hybrid stage-gate plus sprints, a sample sprint plan, and estimation tips.
Read article →Updated 2026-10-07
More guides
Other articles from the Alignlee team.
The Alignlee Mission: Making Consensus Fun and Effortless
Why Alignlee exists: free planning poker with no signup, confidence-weighted votes, and a little fun in the gaps, so estimation stays short and honest.
Read article →Updated 2026-10-07