Agile, Waterfall, or Hybrid? Choosing a Project Approach That Fits the Work
In this Time Limit episode, hosts Nathan Gilmore and John Correlli sit down with digital project manager Brett Harned to weigh agile, waterfall, and hybrid delivery — and to ask whether anyone truly runs 100 percent agile. Episode 2 runs 27:34 and was published 2018-05-01. The three approaches are less about prestige than about how work is sequenced, how much change a team can absorb, and how visible the plan must be to people outside the team. John walks through a quarterly Gantt-chart roadmap that feeds a two-week sprint backlog, and Brett recounts a large university redesign whose sprints had to stretch around stakeholder committees. This guide turns that conversation into a practical way to choose an approach and keep iteration visible on a timeline.
When pure agile is a poor fit
Pure agile depends on conditions that are often missing in real organizations: a team that can stay focused on the work, room to change direction as learning emerges, and leadership support for that flexibility. When those conditions are absent — especially in agencies serving many clients or in teams answerable to many stakeholders — a hybrid model is usually more realistic than insisting on a textbook version of agile.
Use this quick check before choosing:
- Can the team work in a dedicated, stable way, or is attention constantly split across clients and committees?
- Is the solution still unknown and likely to need iteration, or are the steps already known?
- Will leaders accept change during delivery, or do they need a fixed timeline they can point to?
- How many stakeholder groups must approve decisions, and how quickly can they respond?
If the answers point to low stability, high approval friction, and a need for visible dates, plan for hybrid from the start rather than discovering the mismatch mid-project.
Waterfall for known steps, agile for unknown solutions
Waterfall fits work where the sequence is predictable and the deadline is fixed. Construction is a classic example: phases depend on one another in a known order. A webinar launch can behave similarly when the date, speakers, and promotional steps are set in advance.
Agile fits the opposite situation: the right solution is not yet clear, so the team needs short cycles of building, testing, and revising. Choosing based on predictability avoids a common failure — forcing iteration onto work that cannot change, or locking in a detailed plan for work that will inevitably change.
A hybrid pattern: quarterly roadmap, two-week sprints
One practical hybrid pattern keeps two planning horizons at once. A quarterly roadmap, shown as a Gantt chart, sets the broad direction and major milestones. Work for the next two weeks is then pulled from that roadmap into a sprint backlog. As the team learns, the sprint plan can change without rewriting the entire quarter.
This also solves a communication problem. Executives often ask for a timeline even when the delivery method is iterative. Showing sprints as grouped blocks on a Gantt chart gives them that visible timeline while preserving the ability to re-plan inside each sprint. The roadmap stays honest about sequence and dates; the sprint backlog stays flexible about exactly how the work will be done.
Example: stretching sprints around stakeholder committees
A large university redesign illustrates why sprint length itself may need adaptation. Stakeholder committees could not always respond within a standard short cycle, so sprints had to stretch around their meeting and approval rhythms. The lesson is not that agile failed, but that the cadence had to respect the organization's decision speed.
When adapting, ask:
- What is the slowest approval the team must wait for, and can that wait be shortened?
- Which decisions can be delegated to the team instead of routed through a committee?
- Does the sprint length still produce usable feedback, or has it become a mini-waterfall?
Stretching a sprint to accommodate committees can keep work moving, but it reduces the frequency of learning. Where possible, pair a longer cycle with tighter feedback inside it — for example, reviewing partial work with a small stakeholder group before the full committee meets.
Adapt, then revisit as the team grows
Learn each method well enough to know what you are changing and why. Then shape the process around the team you actually have, and revisit that shape as the team grows. A small, dedicated team may sustain pure agile; the same organization two years later, with more clients and stakeholders, may need the hybrid pattern described above.
Revisit the choice whenever any of these change: team size, stakeholder count, deadline rigidity, or how much of the solution is already known. The method should follow the work — not the other way around.
| Approach | Best fit | Watch out for |
|---|---|---|
| Waterfall | Known steps and a fixed deadline, such as construction or a webinar launch | Locking in detail for work that will change |
| Agile | Unknown solution that needs iteration, with a dedicated team and tolerance for change | Assuming stakeholder-heavy teams can sustain pure agile |
| Hybrid | Need for a visible timeline plus iterative delivery, such as a quarterly roadmap feeding two-week sprints | Letting the roadmap become rigid or sprints stretch until feedback is rare |
Summary based on the conditions described in the episode discussion; not a universal rule.