Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology - Recognition Versus Formal Analysis
Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology
Chapter 14. Recognition Versus Formal Analysis
The decision flow is presented as an ordered sequence of questions, but it is important to understand how the framework is applied in practice. In the great majority of cases, a practitioner does not formally walk a Product or Service through each step. The practitioner recognizes the type of work and reaches a sound conclusion directly.
The nature of most work is evident on inspection. An experienced practitioner looking at a web portal application or an extract-transform-load process recognizes immediately that the work decomposes, that it delivers in valuable increments, that those increments can be delivered in consistent cycles, and that the consequence of failure is low — and therefore that the work is Agile-shaped. The same practitioner looking at an integrated circuit, an aircraft, a robotic surgical system, or a merger or acquisition recognizes immediately that the work is composed of large, interdependent units, that it cannot be delivered in valuable increments, and that its consequence of failure is high — and therefore that the work is Waterfall-shaped. The decision flow describes the reasoning, but recognition delivers the answer.
Recognition is reliable at the extremes, where the type of work makes the answer obvious. It is less reliable in the genuinely ambiguous middle, and it is least reliable when a Product or Service is internally mixed — when it contains both work that is clearly Agile-shaped and work that is clearly Waterfall-shaped. For those ambiguous and mixed cases, formal analysis is warranted: the practitioner deliberately works through the decision flow, and, where necessary, decomposes the body of work to examine it more closely. Formal analysis is the exception, reserved for the cases recognition cannot confidently settle. It is not the routine path. A framework that demanded a formal walkthrough for every Product or Service would be too heavy to use; the framework is designed to be applied chiefly by recognition, with formal analysis held in reserve for the cases that genuinely need it.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers