Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology - The Decision Tree

Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology

Chapter 13. The Decision Tree

The framework combines the gate and the structural chain into a single decision flow. The flow is presented below as an ordered sequence of steps. Each step poses one question; the answer either directs the work to a final outcome or advances the evaluation to the next step. The flow is read from the top down, beginning with the gate and ending, for work that reaches it, with the determination of a Hybrid.

Step and Check	The Question	Answer Toward Agile	Answer Toward Waterfall
Step 1 — 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?	Tolerable: continue to Step 2.	Severe: the outcome is Waterfall. The evaluation stops.
Step 2 — Decomposability	Can the body of work be partitioned into small units at all?	Yes: continue to Step 3.	No: the work is monolithic. The outcome is Waterfall. The evaluation stops.
Step 3 — Incremental Deliverability	Can those small units be delivered progressively, each delivered increment having standalone value?	Yes: continue to Step 4.	No: the increments have no standalone value (the aircraft case). The outcome is Waterfall. The evaluation stops.
Step 4 — Time of Delivery	Can those increments be delivered in consistent, committed cycles?	Yes: the work is Agile-shaped. Continue to Step 5.	No: an external constraint forbids consistent cycles. The outcome is Waterfall. The evaluation stops.
Step 5 — Uniformity Check	Is the Product or Service uniform in character, or does it contain work of a materially different character?	Uniform: the outcome is Agile. The evaluation stops.	Not uniform: continue to Step 6 to evaluate a possible Hybrid.
Step 6 — Exception Scan and Isolability Test	Can the minority of exception units be isolated — behind clean interfaces, on separable workstreams, with defined integration points — to run their own cadence without forcing it on the rest?	Yes: the outcome is Hybrid. Name which units break out and where they reintegrate.	No: the exception units are entangled throughout. The outcome is Waterfall.

Two features of the flow deserve emphasis. First, the gate is evaluated before the structural chain, so that a Product or Service whose consequence of failure is severe is directed to Waterfall immediately, without effort being spent on the structural indicators. Second, the three structural indicators form a strict chain: each is evaluated only if the one before it passed, and the work must pass all three to be Agile-shaped. The step at which a Product or Service exits the flow is also its diagnosis. Work that exits at the gate is too dangerous to fail loosely; work that exits at Decomposability is monolithic; work that exits at Incremental Deliverability decomposes but yields no standalone value in its increments; work that exits at Time of Delivery is held to an external clock. Every Waterfall outcome carries with it the reason for that outcome.

Only one path through the flow yields Agile, while several yield Waterfall. This is not a bias toward Waterfall. It reflects the fact that Agile delivery requires a tolerable consequence of failure at the gate and all three structural conditions — decomposability, incremental deliverability, and consistent delivery cycles — to hold together, while Waterfall is the appropriate fallback whenever the gate or any one of the structural conditions fails. Agile is not a harder choice to justify; it is the precise fit for work that satisfies the gate and all three structural conditions, and such work is extremely common in modern software. Waterfall is the honest fit for work that cannot meet them.

Steps 5 and 6 are applied only to work that has been found Agile-shaped by the gate and the structural chain. They determine whether that work is uniformly Agile or is instead a Hybrid. They are described in full in the part on the Hybrid outcome. After the flow has produced an outcome of Agile, Waterfall, or Hybrid, the advisory cost layer is applied, as described in the part on the cost layer.

Legal Disclaimers