You estimate the story at your AI's pace. Your colleague isn't 4 time…
On the same team, AI doesn't save everyone the same time, and a story estimate carries the pace of whoever wrote it. A test to rerun on your last three stories, and an estimation checklist.
You estimate a story at three hours because your AI assistant writes it in twenty minutes. The person who codes it works at another pace, and nobody said which. The story ships with a duration nobody will hit, and at the retro someone asks why AI "doesn't save time". It does, just not the same amount for everyone, and your estimate carries the pace of whoever wrote it. What you leave with: a fifteen-minute test on your last three stories, and a five-question checklist so an estimate says which pace it was made at. What it changes (PO, PM, designer, scrum master, Design System lead): a duration is no longer a number, it is a number plus a speed assumption. Why now: an Anthropic survey from 16 October 2026 puts a figure on the gap between people who already work with AI and the rest. · ·…