December 7, 2025
Deadline drama, anyone?
Estimates are difficult for developers and product owners
Everyone wants dates; no one wants to guess — the comments revolt
TLDR: The article explains why product owners push for estimates while developers resist them. In the comments, people clash over whether estimates help planning or kill learning, with shout-outs to Kanban and the Delphi method. The big takeaway: deadlines vs discovery is the real fight, and it affects what gets built.
A post tries to play marriage counselor between developers (who hate guessing how long features take) and product owners (who need those guesses to plan). But the real fireworks are in the comments. One crowd says estimates are fantasy math for execs who love calendar promises. Another crowd insists you can get “good enough” with experience and back-of-the-napkin numbers. And then a third group lights the match: estimates don’t just fail, they block learning. That’s the mic-drop energy.
The blame game is spicy. One commenter sighs that project managers should be reading this, not devs. Another drags management for wanting promises over progress, while a link-dropper pulls out the Delphi method, an old-school consensus trick, plus the “yes you should estimate” case from Pragmatic Engineer and the debate on HN. There’s Kanban chatter too—think grocery checkout lines for tasks—hailed as effective, but allegedly blocked by promise-hungry bosses. The meme-y mood? “Estimation = astrology for product meetings,” with bonus shade at rigid frameworks that set dates months ahead. The community isn’t just split; it’s a tug-of-war between plan-the-release and let-the-team-learn, and nobody’s putting down the rope.
Key Points
- •Product owners prioritize backlogs because demand for features typically exceeds development capacity.
- •Estimates help POs plan around pre-communicated release dates and, at times, promised release content.
- •POs must balance risk and reward, choosing between large, uncertain features and smaller, safer ones before deadlines.
- •Developers’ input is crucial for sizing work so POs can make informed prioritization decisions.
- •The complexity increases when multiple POs manage parts of a larger product, heightening the need for clear estimates.