{"id":27530,"date":"2026-09-23T17:00:58","date_gmt":"2026-09-23T14:00:58","guid":{"rendered":"https:\/\/www.intellectsoft.net\/blog\/?p=27530"},"modified":"2026-09-23T17:01:18","modified_gmt":"2026-09-23T14:01:18","slug":"stage-gate-process","status":"publish","type":"post","link":"https:\/\/www.intellectsoft.net\/blog\/stage-gate-process\/","title":{"rendered":"Stage Gate Process: Phases, Gates, and Steps Explained"},"content":{"rendered":"

McKinsey’s 2025 analysis<\/span><\/a> of a 16,000-project database found that 8.5 percent hit both their cost and schedule targets. Half a percent delivered every benefit promised at approval. <\/span>Standish Group’s CHAOS<\/span><\/a> data says something similar, but more bluntly: 31 percent of software projects succeed outright, and half land in the “challenged” column. The stage gate process was built to attack that gap. It splits development into fixed stages and puts a formal decision point between each one.<\/span><\/p>\n

Most teams meet the model when a project stops behaving. Requirements drift. A build scoped for four months is in month nine, the budget conversation has climbed two levels of management, and nobody can name the week the scope actually changed. A <\/span>custom software development<\/span><\/a> program running several workstreams at once makes that failure mode routine rather than unlucky. Stage gate governance answers that question directly by defining a point at which the project is halted, a cross-functional review board evaluates the evidence, and the project continues or is abandoned.<\/span><\/p>\n

This article covers all six stages, the contents of a gate review, the criteria used by gatekeepers, the four decisions available, and where the stage gate model grinds against Agile delivery.<\/span><\/p>\n

What Is the Stage Gate Process?<\/b><\/h2>\n

The stage gate process is a project management methodology which involves breaking down the development process into a number of definite stages with specific gates between them. At each gate, a management team reviews the results of the preceding stage and decides whether to move on to the next stage, abandon the project, halt it for some time, or make other recommendations.<\/span><\/p><\/blockquote>\n

Risk in a development program is front-loaded in ignorance and back-loaded in cost. The cheapest week to cancel a weak idea is week two. By week forty the work has an owner, a headcount plan, and a line in the quarterly review, so canceling it becomes a political act instead of a financial one. Gated review moves that decision onto a calendar. Money is released one stage at a time, and the next tranche depends on evidence the previous stage was supposed to produce.\u00a0<\/span><\/p>\n

A project that can’t produce it stops while stopping is still cheap. The framework came out of NPD research and still carries its vocabulary, which is why software teams meet terms like “business case” where they expected “requirements”.<\/span><\/p>\n

Where the Stage Gate Process Came From<\/b><\/h3>\n

Stage-Gate has an author. Dr. Robert G. Cooper, now professor emeritus at McMaster University’s DeGroote School of Business, ran the NewProd studies on new product development through the 1980s. They compared new-product projects that won against ones that died \u2014 hundreds of them \u2014 scored on what the teams actually did rather than what the plan had promised. The winners kept repeating two habits.\u00a0<\/span><\/p>\n

Homework came first: they settled the market case and the technical unknowns before development opened. And one cross-functional team carried the work end to end, with no handoff from marketing to engineering halfway through. Cooper named that sequence Stage-Gate in the mid-1980s. His <\/span>1994 revision<\/span><\/a> loosened the stage-gate model \u2014 stages overlap, and a gate can issue a conditional Go rather than a binary verdict. Pharma and aerospace adopted it quickly. A failed compound or a failed airframe program isn’t something either industry can absorb quietly.<\/span><\/p>\n

How Is the Stage Gate Process Used in Software Development (SDLC)?<\/b><\/h3>\n

The stage gate process doesn’t replace an SDLC but sits above one. A <\/span>software development life cycle<\/span><\/a> describes how code gets specified, built, tested, and released. Stage gate governance decides whether that cycle should run at all, and with how much money behind it.<\/span><\/p>\n

The overlap is what confuses people. Every SDLC already carries milestones \u2014 a design freeze, a code freeze, a release readiness review. What a gate adds is the authority to stop. A design review asks whether the design is ready. A gate asks whether the business case still holds, then funds the next stage or refuses to.<\/span><\/p>\n

The sharper difference sits at the front end. Most SDLC models open at requirements, which quietly assumes somebody already decided the product was worth building. A stage gate development process opens two steps earlier, at discovery and business case, so the requirements phase inherits a decision instead of a hunch.<\/span><\/p>\n

Teams that adopt the model in software usually land somewhere hybrid, close to the Spiral Model or the Rational Unified Process: iterative inside each stage, gated between them. Sprints keep their normal two-week rhythm. The gate falls at the stage boundary, so a review board meets roughly every eight to twelve weeks rather than every sprint.<\/span><\/p>\n

Which Projects Is the Stage Gate Process Good For?<\/b><\/h3>\n