--- title: The Deadline That Was Already Missed, CodeGood | daily.dev description: A case study of a 60-engineer Series C company that missed a promised launch date by seven months despite every task estimate being accurate. The failure... canonical: https://daily.dev/posts/the-deadline-that-was-already-missed-codegood-gf9pdygyg twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The Deadline That Was Already Missed, CodeGood | daily.dev og:description: A case study of a 60-engineer Series C company that missed a promised launch date by seven months despite every task estimate being accurate. The failure... og:url: https://daily.dev/posts/the-deadline-that-was-already-missed-codegood-gf9pdygyg og:image: https://api.daily.dev/og/posts/gF9pDYGYG.png og:image:alt: The Deadline That Was Already Missed, CodeGood og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The Deadline That Was Already Missed, CodeGood **[CodeGood](https://daily.dev/sources/codegood)** · 12 min read · 0 upvotes · 0 comments ## Summary A case study of a 60-engineer Series C company that missed a promised launch date by seven months despite every task estimate being accurate. The failure traced to a missing condition — a vendor identity provider contract that could not support regional deployment within the required timeframe — rather than bad estimation. The piece argues forward planning (listing tasks) misses conditions that others own, while working backwards from a specific outcome (goal regression, as in STRIPS planning and critical path method) surfaces these dependencies early when they are cheap to fix. Includes a cost breakdown showing $165K spent planning backwards versus $4.2M lost planning forwards, and draws on Flyvbjerg's project database, Boehm's cost-of-defect curve, and Kahneman's inside/outside view distinction. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why do software projects miss deadlines even when every task estimate turns out to be correct? Projects miss deadlines when the plan is missing a condition rather than because estimates were wrong. Estimation error is bounded and cancels out across many tasks, but a missing condition — such as a vendor contract requirement nobody flagged — only adds time and has no relation to the size of the plan. A 90-day vendor cycle dropped into a 24-week program causes a 54% overrun that no estimation method could catch. _daily.dev surfaces engineering practices for teams tightening up how they plan and de-risk delivery._ ### What is the difference between forward planning and working backwards for a project roadmap? Forward planning starts from today and lists tasks a team can do, which misses conditions the team doesn't own, like a vendor agreement or regulatory approval. Working backwards starts at the desired outcome and asks what else must be true for it to hold, surfacing both tasks and externally-owned conditions. The method traces to Fikes and Nilsson's 1971 STRIPS goal regression technique used in AI planning. _Developers weighing planning methods can track approaches like this via daily.dev._ ### How much can finding a missing project dependency late actually cost a company? In one documented case, discovering a blocking vendor contract requirement in month four instead of week one cost a company roughly $4.2 million in exposure, including $482,000 in rework, $2.1 million in delayed revenue, and $1.6 million from a lost contract, versus about $165,000 total if the same condition had been found during backward-planning in week one. _daily.dev helps engineering leads keep tabs on planning practices that catch costly risks early._ ## Similar posts on daily.dev - [The Methodology War That Both Sides Lost](https://daily.dev/posts/the-methodology-war-that-both-sides-lost-q71f1cbrj) · CodeGood · 3 upvotes · 1 comments - [dotNetDave Says… Rushing into Coding Without Proper Planning Will Lead to Costly Mistakes and Delays](https://daily.dev/posts/dotnetdave-says-rushing-into-coding-without-proper-planning-will-lead-to-costly-mistakes-and-delays-vifrw1meo) · We Are .NET · 1 upvotes · 0 comments - [Behind Every Successful Software Project Is a Good Plan](https://daily.dev/posts/behind-every-successful-software-project-is-a-good-plan-umsroklgb) · Medium · 2 upvotes · 0 comments - [The Engineering Manager](https://daily.dev/posts/the-engineering-manager-iunymzylz) · Tech Lead Digest · 17 upvotes · 1 comments --- Tags: [#leadership](https://daily.dev/tags/leadership) [View this post on daily.dev](https://daily.dev/posts/the-deadline-that-was-already-missed-codegood-gf9pdygyg) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The Deadline That Was Already Missed, CodeGood","url":"https://daily.dev/posts/the-deadline-that-was-already-missed-codegood-gf9pdygyg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-deadline-that-was-already-missed-codegood-gf9pdygyg"},"datePublished":"2026-08-23T22:18:02.312Z","dateModified":"2026-08-23T22:18:24.716Z","description":"A case study of a 60-engineer Series C company that missed a promised launch date by seven months despite every task estimate being accurate. The failure...","image":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","thumbnailUrl":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","isAccessibleForFree":true,"articleSection":"CodeGood","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"CodeGood","logo":"https://media.daily.dev/image/upload/s--SeDJba6W--/f_auto,q_auto/v1769934638/logos/codegood","url":"https://daily.dev/sources/codegood"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-deadline-that-was-already-missed-codegood-gf9pdygyg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"leadership","timeRequired":"PT12M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"CodeGood","item":"https://daily.dev/sources/codegood"},{"@type":"ListItem","position":3,"name":"The Deadline That Was Already Missed, CodeGood"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-deadline-that-was-already-missed-codegood-gf9pdygyg#faq","mainEntity":[{"@type":"Question","name":"Why do software projects miss deadlines even when every task estimate turns out to be correct?","acceptedAnswer":{"@type":"Answer","text":"Projects miss deadlines when the plan is missing a condition rather than because estimates were wrong. Estimation error is bounded and cancels out across many tasks, but a missing condition — such as a vendor contract requirement nobody flagged — only adds time and has no relation to the size of the plan. A 90-day vendor cycle dropped into a 24-week program causes a 54% overrun that no estimation method could catch. daily.dev surfaces engineering practices for teams tightening up how they plan and de-risk delivery."}},{"@type":"Question","name":"What is the difference between forward planning and working backwards for a project roadmap?","acceptedAnswer":{"@type":"Answer","text":"Forward planning starts from today and lists tasks a team can do, which misses conditions the team doesn't own, like a vendor agreement or regulatory approval. Working backwards starts at the desired outcome and asks what else must be true for it to hold, surfacing both tasks and externally-owned conditions. The method traces to Fikes and Nilsson's 1971 STRIPS goal regression technique used in AI planning. Developers weighing planning methods can track approaches like this via daily.dev."}},{"@type":"Question","name":"How much can finding a missing project dependency late actually cost a company?","acceptedAnswer":{"@type":"Answer","text":"In one documented case, discovering a blocking vendor contract requirement in month four instead of week one cost a company roughly $4.2 million in exposure, including $482,000 in rework, $2.1 million in delayed revenue, and $1.6 million from a lost contract, versus about $165,000 total if the same condition had been found during backward-planning in week one. daily.dev helps engineering leads keep tabs on planning practices that catch costly risks early."}}]} ```