Calibrating Estimates with New and Veteran Members
A new member on an agile team is like a broken thermometer: they don’t yet know what “5 points” means in the context of that particular team. How do you onboard them without losing estimation accuracy?
The Calibration Problem
Every team has its own point scale. An “8” on Team A might be equivalent to a “5” on Team B. When new members join, they bring references from their previous team — or worse, no references at all.
Signs of Poor Calibration
- New members consistently estimate lower — they don’t know the codebase pitfalls yet
- New members consistently estimate higher — insecurity leads to over-estimating as a safety buffer
- Discussions run way too long — the team spends time explaining context for every single estimate
- Velocity shifts abruptly — after members join or leave
Calibration Strategies
1. Observation Period
For the first 2-3 estimation sessions, the new member votes but isn’t counted toward the consensus. They observe how the team estimates and gradually calibrate their internal scale.
2. Reference by Analogy
Present 3-5 previously delivered items along with their estimates:
“Remember that 3-point item? It was a simple form change. The 8-pointer was the payment gateway integration. Use those as your anchors.”
3. Pair Estimation
Instead of estimating alone, the new member estimates alongside a veteran. The dialogue transfers knowledge about the team’s scale and expectations.
4. Familiarization Spike
Before joining estimation sessions, the new member spends 1-2 days exploring the codebase, fixing small bugs, and getting a feel for the architecture.
5. Post-Sprint Review
After the first full sprint, compare the new member’s estimates with actual outcomes:
- “You estimated 3, it took 5. What didn’t you account for?”
- “You estimated 8, it took 3. Did you overestimate?”
This feedback loop accelerates calibration.
Keeping Velocity Stable
When the team changes, velocity changes. Here’s how to handle it:
- New member joining: reduce expected velocity by 20-30% in the first sprint
- Member leaving: reduce proportionally to their historical contribution
- Major change (2+ people): consider velocity “reset” and start measuring fresh
The Role of Veteran Members
Experienced team members should:
- Be patient with disagreements — it’s normal for newcomers to miss the mark on early estimates
- Share context — codebase explanations are an investment, not a waste of time
- Avoid dominating — don’t say “that’s easy, it’s a 2” before the newcomer has voted
When to Re-Calibrate the Entire Team
If velocity still hasn’t stabilized after 3-4 sprints, it may be time to re-calibrate the whole scale. Take items from recent sprints, run a “re-estimation” Planning Poker as a calibration exercise, and adjust the team’s scale.
Conclusion
Calibrating new members is an investment that pays off within a few sprints. With patience, clear references, and post-sprint feedback, new integrants become just as good — and sometimes even better — at estimating as veterans, since they bring a fresh perspective that long-time members may have lost.