DEV

Most project schedules are broken before the first task begins — not because of poor execution, but because effort and duration are silently treated as the same thing. This episode breaks down the estimation trap and offers a practical fix.

Show Notes

Project schedules fail for a reason that rarely gets named directly: the estimates feeding them confuse effort with duration. This episode of Development tackles that specific gap — not as an abstract concept, but as a concrete planning problem with a concrete solution. If your projects consistently run late despite solid teams and genuine commitment, the culprit is almost certainly hiding in how estimates are collected and scheduled from day one.

The episode walks through why the effort-versus-duration confusion is so persistent, what it actually costs in calendar time, and how to restructure the estimation conversation so your schedule reflects reality rather than optimism. Key points covered include:

  • The mental shortcut that breaks every plan: How contributors naturally convert effort hours into calendar days without accounting for anything else filling their week.
  • A worked example with real numbers: Why a 240-hour project for a six-person team does not fit neatly into six weeks — and how quickly the gap widens once realistic availability is factored in.
  • Asking for two numbers, not one: The simple change to your estimation process — capturing focused-work hours and daily availability separately — that produces durations you can actually schedule from.
  • What this means for the critical path: Why a critical path built on effort-only estimates identifies the longest chain of work, not the longest chain of elapsed time — and why that distinction matters enormously.
  • Weekly availability as a scheduling input: How a short, forward-looking team check-in keeps the schedule calibrated as availability shifts during execution.
  • Responding to compression pressure: How to turn "can you go faster?" into a productive trade-off conversation by keeping the math visible and explicit.

The broader argument is that every schedule is a model with assumptions baked in — and the danger is not the assumptions themselves but when they go invisible. Separating effort from availability makes those assumptions explicit at planning time, where they can still be acted on. For teams ready to take the next step, project planning frameworks and the timeline estimator offer structured support for exactly this kind of deliberate scheduling. Listeners who want to explore how AI is changing the way teams surface and manage schedule risk may also find the recent episode The Eval Gap: How to Know if Your Internal AI Tool Actually Works worth a listen.

ProjectManager

RFP

What is DEV?

Software and web development from the side that has to ship it and then live with it. Architecture decisions with a cost attached, scoping, technical debt, hiring and vendor selection, and the AI tooling question every engineering team is now answering whether they planned to or not.

Each episode takes one decision — rewrite or refactor, framework choice, build versus buy, how to scope a fixed-bid project honestly — and works through the tradeoffs, including the ones that only show up in year two. Written for engineering leads, technical founders and the people who fund them. Five or six minutes, no hand-waving.

Topics include rewrite versus refactor, build versus buy, scoping fixed-bid work honestly, technical debt you should keep, framework and platform choices, hiring and vendor selection, code review culture, and where AI tooling actually helps.

Produced by DEV.co, web and software development. Full details, services and further reading at https://dev.co