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

This document presents an IF4IT framework for determining whether a Product or Service should be delivered using an Agile delivery methodology, a Waterfall delivery methodology, or a Hybrid of the two. The framework exists to correct one of the most common and most costly mistakes in enterprise delivery: an enterprise selects a single delivery methodology — often the one its project management office knows best — and then attempts to force every body of work through that one methodology, regardless of whether the work can actually be delivered that way. The reality the framework makes plain is that delivery methodology is a property of the work, not a matter of organizational preference. Certain kinds of work can never fit certain methodologies, and an enterprise that ignores this pays for the mismatch in failed deliveries, wasted investment, and avoidable risk. The framework evaluates a Product or Service against four indicators — Consequence of Failure, Decomposability, Incremental Deliverability, and Time of Delivery — and produces one of three outcomes: Agile, Waterfall, or Hybrid. It is designed to be applied by recognition of the type of work in the great majority of cases, with formal analysis reserved for genuinely ambiguous situations. It is deliberately simple to apply and deliberately honest about what it does not do. This document determines which delivery methodology fits a given Product or Service and explains why. It does not teach how to implement Agile or how to construct a Waterfall delivery pipeline; those subjects belong to other, more explicit documents. The framework recommends and informs. The decisions that belong to the enterprise — what constitutes a Product or Service, when to revisit a past decision, and how to weigh cost — remain with the enterprise.