How to Apply the Framework - Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology
How to Apply the Framework
(Chapter 17 of Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology)
Executive Summary: Chapter Overview
IF4ITThe Bottom Line
Core Concepts
| Concept | Definition & Strategic Role |
|---|---|
| Application Sequence | The ordered procedure for applying the framework from Product or Service identification through outcome determination. It makes the framework repeatable. |
| Fit Before Cost | The methodology fit is determined before cost is considered, preventing budget preference from distorting the assessment. |
| Practical Use | Practitioners may apply the full sequence formally or use it to confirm and communicate a recognized delivery shape. |
Quick Q&A
Question: What is the first step in applying the framework?
Read More Below
Applying the framework to a Product or Service follows a straightforward sequence. The steps below describe the full procedure; in practice, as noted in the part on recognition, an experienced practitioner will often move through the early steps by recognition rather than by formal analysis.
Identify the Product or Service. Establish the defined thing, with its identity and lifespan, to which the framework is being applied. Confirm that the assessment is being made at the onset of the Product or Service’s definition, or that the enterprise has deliberately chosen to reassess an existing Product or Service.
Evaluate the gate. Determine the Consequence of Failure. If a delivered increment failing in use would cause severe harm, the outcome is Waterfall, and the evaluation is complete. If the consequence of failure is tolerable, continue.
Evaluate the structural chain. Determine, in order, whether the work is decomposable, whether its units are incrementally deliverable, and whether its increments can be delivered in consistent, committed cycles. If the work fails any of the three, the outcome is Waterfall, and the evaluation is complete. If the work passes all three, it is Agile-shaped, and the evaluation continues.
Apply the Uniformity Check. Determine whether the Agile-shaped Product or Service is uniform in character. If it is uniform, the outcome is Agile, and the evaluation is complete. If it is not uniform, continue.
Conduct the Exception Scan and the Isolability Test. Identify the minority of units that differ in character from the whole. Determine whether those exception units can be cleanly isolated. If they can, the outcome is Hybrid — name the components that break out to Waterfall and the points at which they reintegrate. If they cannot, the outcome is Waterfall.
Apply the cost layer. With the methodology fit determined, assess whether the enterprise can afford to deliver the work according to that fit. If it can, proceed on the fit. If it cannot, record a deliberate, documented compromise alongside the true fit.
The result of applying the framework is not a single word. It is a small, structured statement: the methodology fit of the Product or Service; for a Waterfall outcome, the indicator that determined it; for a Hybrid, the specific components that break out to Waterfall and the points at which they reintegrate; and, where relevant, the cost-driven compromise the enterprise has chosen and the reason for it. A practitioner who can produce that structured statement has applied the framework completely.
How to cite this page
When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.
Example (informal web citation):
The International Foundation for Information Technology (IF4IT), LLC. How to Apply the Framework | Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology. https://if4it.org/best-practices/agile-waterfall-hybrid-if4it-framework-for-choosing-delivery-methodology/how-to-apply-the-framework/ (accessed 2026-09-11).
See About Us for content governance and site-wide citation guidance.
Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present
Legal Disclaimers