Methodology Madness: Why Managing Projects Isn't About the Buzzwords

My opening disclaimer: I'm not a certified PMP (Project Management Professional), although I have read portions of the PMBOK on multiple occasions. My formal training in PM methods dates back to the mid-late 90s, and maybe it's my strong analytical side, but I've always found sorting through constraints, priorities, risks, timelines, and dependencies to be a fairly straightforward thought process. It's when people and personalities get involved that the struggles sometimes arise. 😊 There, disclaimer over, now onto the crux of the subject.

Waterfall, Agile, Scrum, Kanban. If you've been anywhere near project management in the last decade or two, you've heard these words, maybe a bit too often.

Each approach claims to be the silver bullet, yet if there's one lesson I've learned over the years managing projects across industries and teams, it's this:

It's not about the methodology. It's about getting stuff done. I've experienced this 1st hand over the last few years in a variety of engagements, and I'm going to use this blog to organize my own thoughts.

So, let’s pause for a second and ask ourselves: Have we been overthinking this?

Chasing the Methodology Rainbow

Don’t get me wrong, methodologies matter. Frameworks give us clarity, guardrails, and a shared language. Waterfall lays out tasks in clear, sequential steps, comforting for those who crave order. Agile and Scrum provide speed, iterative execution, and flexibility, especially in software development. Kanban? Well, truthfully, many (yes, I'm raising my hand here as well) still wonder how it slipped into the lexicon (it originated in Toyota’s Lean production methods, not software, after all). I agree that it's great at visualizing work, controlling work in progress, and improving the overall flow. Running projects? Hmmm.

Here's the thing: In practice, projects rarely fit neatly into just one bucket. It's tempting to chase the latest shiny method as if adopting it will guarantee project success. It won't.

I've spent countless hours managing projects using just about every technique imaginable:

• Giant war rooms plastered with sticky notes, whiteboards, and papered walls.

• Meticulous Gantt charts in MS Project, perfectly constructed, until the next day. 🙂

• Slick online tools like Monday or Asana that promise top-notch clarity, collaboration, and speed.

• Energy-charged sprint meetings for development teams.

What did these projects have in common?

They all experienced wins and setbacks, successes and struggles. Some flew; others stumbled. And rarely was the chosen methodology the deciding factor.

The Methodology Isn’t (Usually) the Problem

Projects rarely derail simply because your Kanban board wasn't pretty enough or your Agile cadence wasn’t textbook-perfect. Instead, projects often falter due to real-world issues, such as scope creep, unforeseen constraints, unclear objectives, and inadequate communication.

Here's the paradox I've seen over and over again: when we get too rigidly attached to a methodology, it can blind us to the core truths of project management:

• Clearly defined scope: Know exactly what you’re delivering, and what you’re not.

• Regular, honest communication: Good news fast, bad news faster.

• Visibility and accountability: Know who owns each piece and ensure everyone else is aware of it as well.

• Flexibility to adapt: Because changes will always come. Always.

In short, managing projects is fundamentally about managing expectations, scope, surprises, and communication, not about picking the perfect method from a menu.

Reflecting on My Own Journey

Looking back, some of my most successful projects were developed in makeshift war rooms using paper and markers. Others, using state-of-the-art online tools, failed spectacularly. Why? Because people got hung up on the tools rather than keeping their eyes on the deliverables, the evolving constraints, and inevitable changes that every project experiences.

During one memorable project, we adopted Agile with enthusiasm, embracing the philosophy of sprints, backlogs, and stand-ups. Initially, momentum soared. But soon, unexpected client-driven scope changes overwhelmed the process. The methodology hadn’t failed; it wasn't suited to handle unstructured, rapid-fire external changes. We adjusted our approach, focusing less rigidly on methodology and more on transparent communication and expectation management. It turned the project around.

Another project, managed with classic Waterfall precision, faced delays and frustration when unforeseen resource constraints arose. Again, shifting our attention away from the purity of the method and focusing on managing those constraints collaboratively and transparently brought us back on track.

Even more recently, for a project simpler in scope (four departments, maybe ten people actively involved), a combination of task lists, due dates, and ownership in a PM tool did the trick, simply and effectively, with little bureaucracy to bog us down. It was a home run! Hitting all quality, cost, and delivery milestones!

These experiences reinforced a critical point: tools and methods are valuable, but adaptability, communication, and expectation management are far more crucial.

It’s About Principles, Not Purity

I’m not here to knock methodologies entirely; they have a valuable role. But relying too heavily on any one framework is like trusting that your GPS will never mislead you.

Sometimes, you’ve got to trust your gut, look at the road ahead, and simply adjust course.

The real question isn’t whether to go Agile, Waterfall, or Kanban. It’s whether your chosen approach:

• Clearly sets expectations and scope.

• Provides transparent visibility to everyone involved.

• Enables rapid response to inevitable surprises.

• Keeps communication flowing freely.

Flexibility as the Ultimate Project Management Skill

Great project managers are method-agnostic. They’re less concerned with being textbook-perfect and more focused on asking the right questions at the right time:

• Are we clear about what's expected?

• Does everyone understand their role and deliverables?

• How are we dealing with surprises?

• Are we communicating transparently and frequently enough?

Answering these is where true project management excellence lies.

Keep Calm and Project On

If you’re wrestling with project delivery right now, ask yourself honestly: Are you stuck because of your method, or is something more fundamental amiss?

Take a breath, revisit your goals, and refocus on the things that matter most: clarity, transparency, adaptability, and communication. That's the winning combination, no matter which method you pick.

After all, the best methodology for your project is simple: whatever gets your team delivering results consistently, with the least friction.

In other words, if the method’s not working for you, don’t sweat it. The methodology police aren’t watching.

I promise.

But I'll equally guarantee the results & outcomes police are. Don't lose sight of what really matters.