Spiral Model
Boehm's iterative risk-driven software development model.
The Spiral Model was articulated by Barry Boehm in his 1986 paper 'A Spiral Model of Software Development and Enhancement' (later expanded in IEEE Computer 1988), as an iterative software development model that explicitly addresses risk management at each iteration. Each spiral pass through the four quadrants — Determine objectives, alternatives, and constraints; Evaluate alternatives and identify and resolve risks; Develop and verify the next-level product; and Plan the next phase — produces a risk-driven incremental refinement of the software, with prototyping, simulation, or other risk-reduction work appropriate to the current state of the project. Unlike Waterfall (which assumes risks can be substantially identified and addressed in upfront planning) or pure Agile (which addresses risk through short feedback cycles without explicit risk-driven structuring), Boehm's model places risk identification and reduction at the center of project structure, with each spiral typically more concrete than the last. The model substantially influenced Boehm's later work on Win-Win Spiral and the WinWin Spiral Model integrating stakeholder negotiation. While less commercially adopted than Scrum or Waterfall, the Spiral Model remains an influential reference framework, particularly for risk-heavy projects (defense, aerospace, large enterprise systems) where its explicit risk-driven structuring has clear value.
Core components
- Four quadrants per spiral: Determine objectives/alternatives/constraints, Evaluate alternatives and resolve risks, Develop and verify, Plan next phase
- Risk identification and reduction at each iteration
- Prototyping, simulation, modeling as risk-reduction tools
- Successive spirals produce progressively more concrete and complete artifacts
- WinWin Spiral extension integrating stakeholder negotiation
- Distinction from Waterfall (sequential, low-iteration) and Agile (iterative without explicit risk structuring)
Primary use case
Software development for projects with substantial uncertainty and risk — particularly large, novel, or safety-critical systems; defense and aerospace project management; teaching framework for understanding the role of risk in software development; basis for risk-management practices in mature engineering organizations; reference framework in software-engineering education.
Common criticisms
- Substantial overhead — full spiral discipline is heavyweight relative to agile alternatives that have largely displaced it for most projects
- less commercially adopted than Scrum or even Waterfall in modern industry
- risk-management framing requires capability to identify and quantify risks that many teams lack
- works best for genuinely risk-heavy projects, less well for routine development where risk is largely accidental
- commercial certification ecosystem is small relative to Scrum or PMP
- later iterations within the model can drift toward Waterfall structure if discipline lapses
- Boehm's WinWin extension addressed some critiques but added further complexity
- the spiral diagram's apparent intuitive simplicity can mask the practical difficulty of executing the model.
Lineage
- Siblings
- Waterfall Model