The fixed-scope build

Every build we run has a fixed box. Not a quarter, not "however long it takes." A scope agreed at the end of Discovery, a set number of two-week sprints, and a real thing in production on the last day of the last sprint. The box isn't magic. It's calibrated. Each two-week sprint ends with a demo, so a surprise — a vendor outage, a stakeholder on vacation, a spec that turned out to be wrong — costs days, not months. A quarter-long plan with no checkpoints is long enough that anyone can hide inside it; by week eight, the team has forgotten what they promised in week one. A fixed number of sprints is short enough that no sprint is optional, and long enough to absorb one bad week without missing the ship date. What fits in a short build — two or three sprints: a working contact-and-booking flow with a real database and real email. A new internal dashboard connected to two or three existing data sources. A pricing page A/B test rig with analytics that actually attribute. The migration of one system from a legacy stack to a modern one — not the whole legacy stack, one system. A small AI feature grafted onto an existing product, end-to-end, including its evaluation harness. What does not fit: rebuilding your entire stack. Replacing your team's workflows with a brand-new tool. Anything that requires three departments to agree on a definition before development can start. If the scope calls for those, that's what Discovery is for: a two-week, fixed-fee audit that ends with a decision and a priced, scoped Proposal. Then the build starts. The cutting discipline matters. Halfway through the build we look at the plan and ask which items, if we dropped them, would still leave a shippable thing on the last day. Anything on that list is a candidate for the next engagement, not this one. Almost every project sheds one or two things in that meeting. The teams that don't do this meeting are the teams that miss the date. If a vendor is telling you their build is "about halfway done" in month four, ask them what shipped in the last sprint demo. If the answer is "well, we're still integrating…" — you don't have a build, you have a subscription to their calendar.