Robert G. Cooper's stage-gate process breaks new product development into six phases (discovery, scoping, business case, development, testing, launch), each gated by a cross-functional go/kill/hold review. Kill decisions cluster hardest at gate 2, the business case review, once real financial assumptions replace early estimates. The piece covers when to use full stage-gate versus a lightweight or hybrid stage-gate-agile approach, gate output requirements per stage, and benchmarking data on project governance performance, framing the choice as matching gate weight to capital risk rather than picking Stage-Gate versus Agile outright.
Table of contents
What is the stage-gate process? (TL;DR)Where the stage-gate model came fromThe six stages, from discovery to launchWhat happens at each gateGate outputs: Inputs and criteria a review needsWhen to build stage-gate vs when to skip itStage-gate vs agile methodology: Which fits a software team?Benefits, disadvantages, and where stage-gate failsFAQ: Stage-gate process questionsBuild your stage-gate process with NetguruQuestions this post answers
At which gate in the stage-gate process do most project kill decisions happen?
Kill decisions cluster most heavily at gate 2, the business case review, right after real financial assumptions replace early estimates. Projects that passed the earlier scoping gate on optimism alone tend to fail once cost-to-build estimates, revenue models, and competitive analysis are scrutinized. Later gates rarely kill projects because sunk cost and momentum take over. Teams weighing go/kill decisions can track project governance practices like this on daily.dev.
Should a small software team use a full stage-gate process or Agile for a new feature?
A four-person team shipping something like a new checkout flow does not need a five-gate phase-gate process; it needs a hypothesis, a two-week build, and real usage data. Stage-Gate earns its keep on capital-intensive, hardware, or regulated projects where a wrong go decision costs real money before shipping, while Agile suits low-cost digital features where a bad bet only costs a sprint. Developers deciding between Agile and heavier governance models can follow this debate on daily.dev.
What percentage of top-performing companies use a hybrid Agile-Stage-Gate model?
44.8% of top-performing companies successfully used an Agile-Stage-Gate hybrid model, according to a Danish manufacturing-firm study by Cooper and Sommer. In this hybrid, sprints run inside each stage while a lightweight gate with a weighted scorecard sits at the boundary between stages, preserving governance without gating every sprint. Engineering leaders comparing hybrid delivery models can keep up with findings like this on daily.dev.