A new Product Owner at Nestbot insists that every Product Backlog item must be sized in story points before Sprint Planning, calling it "a Scrum requirement." A Developer pushes back. According to the Scrum Guide, is a specific estimation unit like story points required?
Select an answer to reveal the explanation.
Short Explanation
Story points feel like Scrum because so many teams use them, but the Guide itself never says the word. It leaves how you estimate completely up to the team, whether that's story points, hours, or no formal estimate at all. "A Scrum requirement" is doing a lot of work in that sentence, and it's not true.
Full Explanation
The Scrum Guide deliberately does not prescribe any particular estimation technique or unit; sizing Product Backlog items, if a team chooses to do it at all, is left entirely to the people doing the work. Story points are a widely adopted practice, not a Guide requirement, so calling them mandatory overstates what the framework actually says. Claiming they're required only above a size threshold invents a rule with no basis in the Guide, which draws no such distinction because it doesn't mandate estimation units at all. Substituting hours as the "real" required unit makes the same mistake in a different direction, prescribing something the Guide is silent on. The actual requirement is lighter: the Product Backlog needs enough information, including some sense of size where useful, for the Product Owner to order it and for Developers to forecast, but the technique for getting there is a team choice. A practical check for Nestbot: if the Product Owner points to "the Scrum Guide" to justify a specific estimation method, ask them to find the actual sentence; they won't, because it isn't there.