A Final Note to Practitioners

This framework exists to replace a habit with a discipline. The habit is the selection of a single delivery methodology by organizational preference, followed by the imposition of that methodology on every Product or Service the enterprise delivers. The discipline is the recognition that delivery methodology is a property of the work — that it is determined by the intrinsic nature of the Product or Service, evaluated honestly against the Consequence of Failure and the three structural indicators of Decomposability, Incremental Deliverability, and Time of Delivery.

Applied well, the framework is quick. An experienced practitioner recognizes the type of work and reaches a sound conclusion directly, using the decision flow chiefly to confirm and to communicate that conclusion. Applied honestly, the framework protects the enterprise from the costly mismatch of methodology to work — from forcing iterative delivery onto work that cannot accept it, and from burdening naturally iterative work with staged delivery it never needed. And applied with discipline, the framework keeps its three outcomes meaningful: a Hybrid that is earned rather than assumed, and a cost-driven compromise that is documented rather than hidden.

The framework recommends and informs; it does not govern. What constitutes a Product or Service, when to revisit a past decision, how to calibrate the terms small and severe for the enterprise’s own context, and how to weigh the cost of delivery against the enterprise’s tolerance for it — these are decisions that belong to the enterprise. The framework’s role is to help the enterprise make those decisions well, with a clear view of what the work genuinely requires. This document determines which delivery methodology fits a Product or Service and explains why. How to practice Agile, and how to construct a Waterfall delivery pipeline, are the subjects of other, more explicit documents, to which the practitioner who has chosen a methodology should turn next.