15. Mastering Project Management: Waterfall or Agile for Project Success

Being stranded at Universal Studios taught podcast host Brittany Wilkins a valuable lesson—traditional methods still work. In this episode, she shares how that unexpected moment sparked a deeper realization about project management: the importance of knowing when to choose Agile, Waterfall, or a hybrid of both.

🚖 Agile is the Uber. Waterfall is the taxi.
Both have value. Both have a place. The smartest project leaders know which ride to take based on the road ahead.

💡 What You'll Learn:

• Why Waterfall still works for projects requiring structure, compliance, and predictability
• When Agile thrives in fast-paced, feedback-driven environments
• How to build a hybrid approach that combines the best of both worlds
• Real-world analogies and case studies to help you make smarter project decisions

Plus, Brittany gives a special shoutout to new listener Megan, who’s transitioning into project management and already finding value in the Masterclass community.

🔹 Subscribe to exclusive bonus episodes and elevate your project management career with insider insights, advanced strategies, and expert guidance!

https://www.buzzsprout.com/2308468/subscribe

Transcript

Thank you for tuning in to Project Management Masterclass. I truly appreciate each and every one of you for taking the time to listen and grow with this show. Today, I want to give a special shoutout to Megan, a new listener who recently reached out to me on LinkedIn. Her message reads:

I’m a new listener to the Project Management Masterclass, and I wanted to thank you for the content that you provide on that platform. As an educator looking to explore a career shift into project management, I’ve found your podcast to deliver a wealth of information and insight. I look forward to following your future episodes, and I would appreciate the opportunity to connect with you here as well!

Thank Megan I really appreciated your message. Thank you for making project management masterclass part of your journey. Project management community welcomes you. Stay tuned Megan I will be checking in on how your transition is going. 

Whether it be fanmail or linkend in message I love reading and connecting with listeners of the show. Feel free to reach out to me. Contact details in the show description. 

Now on to todays show. 

I’ll be honest—I haven’t taken a taxi in years. But there I was, standing outside Universal Studios, exhausted after a long day, trying to get an Uber back to my hotel. My phone was at 10%, the app kept showing ‘No drivers available,’ and surge pricing had doubled the fare. I waited, refreshed the app, waited some more… nothing.

Then I turned around and saw a taxi stand. No app needed, no price hikes—just a ride waiting for me. For the first time in five years, I took a taxi. And you know what? It worked, just like it always has.

That got me thinking—how often do we rush to embrace new ways of working while completely ignoring the old methods that still get the job done? And in project management, we see this all the time. Agile is the shiny Uber, and people act like Waterfall is outdated. But just like taxis, Waterfall still has a place. In today’s episode, we’re talking about why you need both and how smart project managers know when to use each. 

HOST:

We’ve all seen how ride-sharing apps like Uber and Lyft disrupted the traditional taxi industry. But did taxis disappear? No. Because despite all of Uber’s innovations, taxis still have advantages—fixed pricing, no surge fees, and you don’t need an app or a charged phone to get a ride.

Uber brought speed and convenience, but it didn’t replace taxis—it simply created another option. And in many cases, taxis adapted by integrating app-based booking, similar to Uber.

Now, let’s bring this back to project management. Agile is often seen as the Uber of project management—fast, flexible, and modern. Meanwhile, Waterfall is the traditional taxi—structured, predictable, and reliable. But just like taxis, Waterfall isn’t going anywhere.

In fact, depending on your project, it might still be the best option. The key isn’t choosing one over the other—it’s knowing when to use each.” Or in some cases you may not have a choice.You take what the process give me execute project.  Here what I mean many of the large corporate companies I been apart have well established NPD process that is the methodology to follow. From my experience within NPD we have a waiver process for each phase gate. There are things on checklist that may not be applicable so the team has gotten approval from RDL robust design leader to waive backed by the justification.in a way there is agility in waterfall methodology 

So why is Waterfall still relevant? Simple—because some projects require structure and predictability. Here’s where Waterfall excels:

 1. Fixed Scope & Predictability – If you’re working on a project with clear, well-defined requirements—like building a bridge, launching a government program, or rolling out a pharmaceutical product—Waterfall ensures that every phase is planned before execution.

 2. Heavy Documentation & Compliance – Industries like healthcare, finance, and construction have strict regulatory requirements. You can’t afford to ‘iterate’ your way through FDA approval.

 3. Risk Management & Stability – In large-scale projects, stability often matters more than speed.

Let me give you an example—imagine trying to construct a 50-story skyscraper using Agile. You wouldn’t want to be halfway through building the foundation while already testing out the rooftop lounge, right? That’s why construction follows a linear, structured process—exactly what Waterfall is designed for.”

But Agile is the future, right? Well… yes and no. Agile is incredibly powerful, but it’s not a one-size-fits-all solution. Agile works best when:

 1. Requirements Are Unclear or Rapidly Changing – If you’re developing software, launching a startup, or testing new product features, Agile allows you to pivot fast based on feedback.

 2. You Need Speed & Flexibility – Instead of spending months defining every detail, Agile lets you release small, working versions and improve them over time.

 3. Collaboration is Key – Agile thrives in environments where teams work closely with stakeholders and customers, adjusting deliverables based on real-time input.

Let’s say you’re developing a new mobile app. You don’t want to spend a year designing something, only to find out users hate the layout. Agile helps you adapt and refine as you go.

So here’s the big takeaway—Waterfall and Agile aren’t enemies. In fact, the best project managers know how to blend the two.

Here are a few ways they can coexist:

 1. Agile for Software, Waterfall for Infrastructure – Imagine a company building a new hospital. The physical construction follows Waterfall, but the software for patient management? That’s best developed using Agile.

 2. Agile Inside Waterfall – Some teams run Agile sprints for development but use Waterfall for overall project planning and approvals.

Modular initiatives case study

 3. Scaled Agile Frameworks (SAFe & Disciplined Agile) – Many large companies use Agile at scale while keeping some governance elements from Waterfall.

Think of it like Uber introducing scheduled rides—you get flexibility, but with the predictability of a traditional taxi service.

So, what’s the lesson here? The best project managers aren’t stuck in one mindset. They know when to go Agile, when to go Waterfall, and when to mix the two. Just like taxis and Uber, both have their place—it’s all about choosing the right tool for the job.

Don’t over analyze it. Start with what you have.  

Now, I want to hear from you. Have you worked in both Agile and Waterfall environments? What’s your experience with hybrid models? Drop me a message, leave a review, or connect with me.  

And if you found today’s episode valuable, be sure to subscribe to Project Management Masterclass so you never miss an insight that can level up your career. Until next time, keep leading, keep learning, and keep delivering!