How do you accurately estimate story points for complex tasks in a newly formed Scrum team?

All answers to this question.

The key to relative estimation is finding your "Golden Reference." Pick a story that everyone understands—something simple like a basic login page—and call that a "2." Then, compare everything else to that. Is this task twice as hard? Then it is a "5." Is it four times as hard? That is an "8." Don't get hung up on hours. Points are about complexity, risk, and effort combined. After 3-4 sprints, look back at the stories you completed. If you find a "3" that took longer than an "8," discuss why in your Retro. Your baseline will naturally emerge through consistency.

   Answered 2024-05-24 by Susan White

Have you considered T-shirt sizing (S, M, L, XL) instead of numbers for the first few sessions? Sometimes taking the math out of the equation helps teams focus on the relative size more intuitively.

   Answered 2024-05-28 by Richard Harris

• Richard, we actually tried T-shirt sizing last month. It helped with high-level grooming, but the team struggled to translate that into velocity for the sprint. We eventually mapped S=2, M=5, L=8 to get the best of both worlds. It seems to have stabilized our planning sessions significantly because people aren't over-analyzing the specific digits as much.

     Commented 2024-06-01 by William King

Use a "Reference Board" where you pin examples of past tasks next to their points. This gives the team a visual guide during every planning session to ensure consistency.

   Answered 2024-06-05 by Linda Garcia

• Linda's' suggestion is vital. Having those visual anchors prevents "point drift" over time. I've seen teams slowly turn a 3 into a 5 without realizing it; a reference board stops that.

     Commented 2024-06-07 by Brian Anderson