
Agile Mentors Podcast from Mountain Goat Software #174: Why Estimating Still Matters with Mike Cohn
Feb 11, 2026
Mike Cohn, agile practitioner and CEO of Mountain Goat Software, shares his take on estimating and planning. He explains why estimates provoke strong reactions. He contrasts story points and hours, discusses the no-estimates movement, and recommends estimating only when it informs decisions. He also covers flow metrics, responsible ranges, and ways to keep planning from harming trust.
AI Snips
Chapters
Transcript
Episode notes
Treat Story Points As Effort Not Time
- Use story points as an abstraction measuring effort from complexity, risk, uncertainty, and volume rather than mapping them to time.
- Mike warns against treating points as days because that misunderstanding causes wide misuse.
Use Quick Guesses To Size Sprints Then Drop Them
- In sprint planning, start with quick, 30-second estimates on sprint backlog items but drop them later if the team proves reliable.
- Use those quick estimates only to decide how much work to pull into the sprint.
Estimates Exist To Enable Tradeoff Decisions
- Estimation's core purpose is enabling decisions: a product owner may accept a 3-point feature but reject it at 20 points.
- Sprint-level estimates also spark design conversations that can trade programming for testing time to reduce overall cost.

