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

The third and final link in the structural chain is Time of Delivery. It asks whether the individually valuable increments of the work can be delivered in consistent, committed cycles. It presupposes Incremental Deliverability — there is no point asking how often increments can be delivered if there are no valuable increments to deliver — but, like the other links, it is a genuinely separate question.

The test of Time of Delivery is the ability to commit to a consistent delivery cycle. It is not a test of absolute speed. As described in the Conceptual Foundations, a delivery cycle is most commonly one to four weeks in length, but the length is a reference point, not a rule. What matters is that the team can commit to delivering increments in a consistent, repeatable cycle. A team that can reliably deliver an increment every four weeks satisfies the Time of Delivery indicator just as fully as a team that delivers every two weeks; the consistency and the commitment are what the indicator measures.

A body of work can be incrementally deliverable and still fail the Time of Delivery indicator, because delivery time is constrained not only by the nature of the work itself but by factors external to it. Procurement lead times, dependencies on other parties, mandated waiting and approval periods, and physical or process constraints can all impose duration on the delivery of an increment regardless of how cleanly the work decomposes or how valuable each increment would be. A body of work whose increments cannot be delivered in consistent, committed cycles — because an external clock governs their delivery — is directed to Waterfall, even though it is both decomposable and incrementally deliverable. A body of work that passes all three structural indicators, having already passed the gate, is Agile-shaped.