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

The following brief illustrations show the framework reaching its three outcomes by recognition of the type of work. They are deliberately short. They are not detailed case studies; they are examples of how a practitioner recognizes the nature of a Product or Service and reaches a sound conclusion.

A web portal application is a characteristic Agile outcome. Its consequence of failure is typically low — a defective feature is a recoverable, inexpensive problem. Its work decomposes readily into small units. Those units are incrementally deliverable: a single new feature provides standalone value on delivery. And those increments can be delivered in consistent, committed cycles. The portal passes the gate and all three structural indicators, and if its work is uniform in character, the outcome is Agile. The portal is not delivered as a project; it is improved continuously, as a stream of delivered increments, over a lifespan that may extend for decades.

An integrated circuit is a characteristic Waterfall outcome. Its consequence of failure is severe in economic terms: an error discovered after fabrication requires a costly and time-consuming chip turn. On the gate alone, the integrated circuit is directed to Waterfall. Even setting the gate aside, the work is composed of large, deeply interdependent units that do not yield standalone value when delivered in isolation. The integrated circuit is delivered as a bounded, staged effort, with extensive verification — simulation and emulation — before fabrication, precisely so that failure is detected before the expensive and irreversible step of manufacture.

A large enterprise software platform that is predominantly Agile but contains a regulated, high-consequence component — for instance, a component subject to strict financial-compliance verification — is a characteristic Hybrid outcome. The bulk of the platform decomposes, delivers in valuable increments, and is delivered in consistent cycles, with a low consequence of failure: it is Agile-shaped. But the regulated component carries a severe consequence of failure and must be delivered through staged, formally verified Waterfall delivery. If that component can be cleanly isolated — placed behind a clean interface, developed on a separable workstream, and reintegrated with the rest of the platform at defined points — the outcome is a genuine Hybrid: the platform is delivered predominantly as an Agile stream, the regulated component breaks out as a bounded Waterfall effort, and the two reintegrate at the defined points. If the regulated component cannot be isolated — if it is entangled throughout the platform — the outcome is Waterfall for the platform as a whole.