OneMorePoint

Agile & Scrum Blog

Practical tips on Scrum Poker, story points, and agile estimation, written for teams running real sprints, not to rank for a keyword. Looking for in-depth guides instead? See our guides.

Cover illustration for "How to Estimate a Migration or Replatform"
Latest
Advanced

How to Estimate a Migration or Replatform

Migrations are the work teams underestimate most reliably. The reason isn't optimism about the hard parts; it's forgetting the long tail entirely.

43 more articles

  • Cover illustration for "When the Deadline Is Fixed and the Estimate Doesn't Fit"
    Process

    When the Deadline Is Fixed and the Estimate Doesn't Fit

    Sometimes the date genuinely can't move. Re-estimating until the numbers agree with it is the worst available response. Here are the ones that actually work.

  • Cover illustration for "Estimating Work That Depends on Another Team"
    Advanced

    Estimating Work That Depends on Another Team

    Cross-team dependencies are where estimates quietly fall apart. Here's how to size work you don't fully control without inflating every number "just in case".

  • Cover illustration for "How to Estimate Performance and Optimization Work"
    Advanced

    How to Estimate Performance and Optimization Work

    "Make the dashboard faster" is almost impossible to estimate as written. Here's how to turn performance work into something a team can size and actually finish.

  • Cover illustration for "Estimating Stories That Cross Frontend and Backend"
    Team Dynamics

    Estimating Stories That Cross Frontend and Backend

    When a story needs both frontend and backend work, the vote often splits along specialty lines. Here's how to get one honest number without splitting the team.

  • Cover illustration for "Does Planning Poker Work for Kanban Teams?"
    Advanced

    Does Planning Poker Work for Kanban Teams?

    Planning poker is built around sprints, but plenty of flow-based teams still want a consistent way to size work. Here's how to adapt it when there's no sprint boundary.

  • Cover illustration for "Why Story Points Inflate Over Time (And How to Stop It)"
    Process

    Why Story Points Inflate Over Time (And How to Stop It)

    A "5" today isn't the same size as a "5" a year ago on most teams. Point inflation quietly breaks velocity as a planning tool. Here's why it happens and how to reset it.

  • Cover illustration for "The Scrum Master's Role in Planning Poker"
    Team Dynamics

    The Scrum Master's Role in Planning Poker

    A good facilitator makes planning poker fast and honest; a bad one makes it a rubber stamp. Here's what the Scrum Master should actually be doing during estimation.

  • Cover illustration for "5 Common Planning Poker Mistakes (And How to Fix Them)"
    Fundamentals

    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.

  • Cover illustration for "Estimation Anti-Patterns That Kill Sprint Velocity"
    Process

    Estimation 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.