Introduced in the mid-1980s by Dr. Barry Boehm, the Spiral model does a much better job of managing risks through one of its core attributes as a process generator. Through multiple successive iterations—starting with a firm set of requirements—the concept of operations (CONOPS) is established, requirements are developed (before Spiral development actually starts), the product is developed, tested, verified/validated, and finally released.
The Spiral methodology was originally created for software. Each iteration in this model:
- Evaluates or reevaluates what the conditions of project success mean for stakeholders
- Determines whether alternative approaches are needed to achieve project success
- Evaluates risks from the selected approach ...