The Universal 'Two Weeks' Software Development Estimate
Description
A popular meme format featuring a dialogue at the top followed by a reaction image. The text reads: 'Project Manager: How long will it take to implement this feature? Me: Two Weeks. Project Manager:'. Below this text is a still image of Daenerys Targaryen from the TV series Game of Thrones. She has long, braided, platinum-blonde hair and is looking slightly upwards at someone off-screen with a tight-lipped, knowing, and deeply skeptical smile. The humor is derived from the shared understanding in the tech industry that 'two weeks' is a notoriously common, often wildly inaccurate, placeholder estimate for any task of moderate complexity. The project manager's expression perfectly captures the seasoned veteran's reaction to this trope: a mix of feigned acceptance and deep-seated doubt, born from years of hearing the same optimistic timeline that rarely accounts for unforeseen complexities, bugs, or scope creep
Comments
8Comment deleted
In software, 'two weeks' is the atomic unit of work estimation. It's indivisible, universally understood to be fiction, and has a half-life of about three days
I’ve started calling “two weeks” the developer’s Dracarys - utter it, the PM falls silent, and by sprint three the cone of uncertainty is just charred rubble
The PM's already mentally calculating how many "two weeks" iterations it'll take before we discover the API we're integrating with uses SOAP, the data model requires a complete refactor, and half the team will be pulled into a P0 incident from the last "two week" estimate
'Two weeks' is the TCP of estimates: everyone sends it, nobody believes it arrives intact, and the retransmission happens at the next standup
Ah yes, the classic 'two weeks' estimate - the developer's equivalent of 'famous last words.' That smile? That's the PM mentally multiplying by π, adding the Fibonacci sequence, and already scheduling the retrospective where we'll discuss why it actually took six sprints. They've seen your Git history; they know about your 47 open browser tabs of Stack Overflow, and they're already preparing the 'just one small change' that will turn your elegant microservice into a distributed monolith. Two weeks? Sure, if we're only counting the time you're actually coding and not the three days lost to dependency hell, the surprise database migration, and that one legacy module nobody mentioned that's written in a dialect of JavaScript so ancient it predates JSON
Two weeks: the only estimate unit where PMs get precision and architects get plausible deniability for the inevitable monolith refactor
“Two weeks” is Schrödinger’s estimate - engineering means one sprint with discovery, refactors, schema migrations, and a CAB sign‑off; PM hears “Friday.”
Two weeks is a unit‑test estimate - green on my laptop, red in integration, instantly promoted to an SLA