Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology - Overview of the Framework
Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology
Chapter 8. Overview of the Framework

The framework evaluates a Product or Service against four indicators and produces one of three outcomes. In evaluating a Product or Service, the framework examines the body of work required to create and improve it; the phrases the body of work and the Product or Service are used accordingly, the first referring to the work of delivering the second. The four indicators are not co-equal. One of them — Consequence of Failure — acts as a gate: it is evaluated first, and a severe consequence of failure determines the outcome on its own, regardless of the other three indicators. The remaining three indicators — Decomposability, Incremental Deliverability, and Time of Delivery — form a structural chain, evaluated only for work that passes the gate. They are ordered deliberately, because each depends on the one before it, and a body of work must satisfy all three to be considered Agile-shaped.
| Indicator | Role | The Question It Asks |
|---|---|---|
| Consequence of Failure | Gate | If a delivered increment fails in use, is the harm severe — harm to humans, material brand damage, regulatory or legal breach, or irreversible loss? |
| Decomposability | Structural chain, 1st | Can the body of work be partitioned into small units at all? |
| Incremental Deliverability | Structural chain, 2nd | Can those small units be delivered progressively, each delivered increment having standalone value? |
| Time of Delivery | Structural chain, 3rd | Can those increments be delivered in consistent, committed cycles? |
The three outcomes are Agile, Waterfall, and Hybrid. A Product or Service is Agile when it passes the gate and satisfies all three structural indicators, and is uniform in character. It is Waterfall when it fails the gate, or fails any one of the structural indicators, or is so entangled that no part of it can be isolated for separate delivery. It is Hybrid when it is predominantly Agile-shaped but contains a minority of components that are Waterfall-shaped and that can be cleanly isolated from the rest. After the methodology fit has been determined, a separate and advisory cost consideration is applied; it never changes the fit. The parts that follow describe each indicator, the decision flow that combines them, the role of recognition, the Hybrid outcome, and the cost layer.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers