Why Developers Should Give Estimates

Stop Inflicting Daily Standups and Computer Science Riddles on Your Devs - David Guttman

Topic 7 of 8

Published Feb 3, 2025 · Clip 43:12–55:56 (12:44)

David argues developers should give estimates because the act of estimating itself keeps projects on track—once stated, the estimate becomes a budget that counters tendencies to overreach or chase tangents. Accuracy isn't the point; estimates should update as developers learn more, and the real signal is whether estimates keep moving and don't converge. He addresses the micromanagement objection (it's treating devs like adults, like asking a mechanic for a timeline), notes that big estimates trigger valuable scope conversations (e.g., 'we just need a demo that works once' can turn four weeks into an hour), and stresses that scope and date can't both be fixed—one must be flexible. Managers check in at 50%/75% milestones so updates feel natural rather than final.