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

The framework produces one of three outcomes. They are introduced here so that the reader understands the destinations before studying the route.

The first outcome is Agile. Work suited to Agile delivery exists as a continuous stream of small, independent units — commonly expressed as User Stories tied to Enablers and Epics — each individually valuable, delivered in consistent, committed cycles. There is no project. The Product or Service simply continues to be improved, one delivered increment after another, for as long as the enterprise chooses to invest in it. A web portal application and an extract-transform-load process are characteristic examples of work that is naturally Agile-shaped.

The second outcome is Waterfall. Work suited to Waterfall delivery exists as a bounded, integrated effort that must be delivered as a whole. It advances through a sequence of stages, with formal verification at each stage, and the complete Product or Service is delivered only when the effort concludes. This work genuinely is a project, because it genuinely has edges. An integrated circuit, an aircraft, and a complex organizational undertaking such as a merger or acquisition are characteristic examples of work that is naturally Waterfall-shaped.

The third outcome is Hybrid. A Hybrid Product or Service is delivered predominantly as an Agile stream, but it contains one or more bounded, integrated components that must be delivered through Waterfall. Those components are isolated from the Agile stream, delivered through their own staged effort, and reintegrated with the rest of the work at defined points. A Hybrid is, in this sense, an outcome reached from the Agile side: it arises when work that is otherwise Agile-shaped proves not to be uniform, and a minority of Waterfall-shaped components must break out of the Agile stream. The framework does not define a mirror-image outcome in which a predominantly Waterfall effort contains isolated Agile pockets; work that is Waterfall-shaped overall is delivered as Waterfall. The Hybrid is a genuine and common outcome, because real Products and Services are frequently not uniform in character. It is also the outcome most easily misused, and the framework therefore holds it to a strict standard: a Hybrid must be earned by demonstrating that its Waterfall components can be cleanly isolated. A Hybrid is never a default and never a way of avoiding a difficult decision.