Do All Project Managers Work the Same Way?
📌 Introduction:
No – there are various methodologies they can use, such as Waterfall or Agile. Personally, I prefer a hybrid of these if there’s a client with a budget and a timeline.
But it isn’t only about the methodology—the size of the company, the size of the project, and the industry impact what’s important to both the projects and their Project Managers (PMs). Many PMs also adapt methodologies rather than following them rigidly. For example, PRINCE2 is a great framework, but it could overwhelm some projects.
Let’s break down each approach with a touch of real-world practicality and a few insights from someone who’s been in the trenches.
🙌 Quick Read - Key Takeaways
📌Waterfall project management works well for projects with predictable workflows.
📌 Agile project management is ideal for teams needing flexibility and fast feedback loops.
📌 Many businesses use a hybrid approach, blending Waterfall’s structure with Agile’s flexibility.
😉 Long(ish) Read
Waterfall – The Traditional Approach
This linear process works well when the project is predictable and well-defined. This is the methodology that embodies Benjamin Franklin’s quote: “If you don’t plan, you plan to fail.”
❓How It Works:
Agree on what needs to be done, by when, and within what budget.
Gather requirements upfront.
Build or develop the product.
Test to ensure it works.
Deliver the final product.
🗝️ Key Elements - Planning Is Crucial:
Thorough planning should take up a big chunk of time at the start of the project to address the validity of requirements, risks and issues upfront.
Poor planning leads to delays and budget overruns.
⚠️ Downside:
Hard to adapt quickly to changes and errors.
Fixing mistakes can be costly.
💡 Real Talk:
You must plan. The whole project. No crossing your fingers, starting to deliver after drawing out your plan on a napkin, and hoping for the best!
That’s why being a Project Manager is a full-time job. We’ve all seen those house design fails—let’s avoid that.
Agile – The Modern Approach
Agile is a fantastic approach, but beware of misconceptions. ⚠️ Agile doesn’t mean “do whatever you want and change it whenever.” It still has rules.
Agile is iterative, meaning the process repeats in cycles (called sprints). Each sprint delivers a functional part of the project.
🔁 Sprint Process:
Gather requirements → Design → Develop → Test → Deliver → Repeat until complete
✨ Benefits:
Stakeholders see progress every 2–4 weeks.
Mistakes are caught and fixed early.
Adaptable to changes (e.g., company restructures, new tech).
⚠️ Challenges:
Agile works best without strict deadlines or budgets.
Poor understanding of Agile leads to scope creep—when the project keeps expanding beyond its original scope.
💡 Real Talk:
Agile is great until someone hears “flexible” and thinks it means “build me a spaceship instead of the car we agreed on.” Spoiler: No, you won’t hit the deadline.
Let’s compare
🔗Want to Learn More?
Explore the rest of this blog series:
📌 Task Management vs. Project Management: What’s the Difference?
Are you really managing projects—or just tracking tasks? Here’s the key difference and why it matters.
🟡 Do All Project Managers Work the Same Way? ⬅️
Spoiler: No. Waterfall? Agile? A little bit of both? Let’s break it down.
📌 Agile plus Waterfall – The Best of Both Worlds
Why choose when you can blend structure with flexibility? Hybrid project management explained.
📌 How Does a PM Track All of This Work?
Post-its? Spreadsheets? Or… something smarter? Here’s what works (and what really doesn’t).
📌 When Do I Not Need Specialized Software?
Surprising answer: Not always. Here’s when a PM tool is worth it—and when it’s just extra noise.
📌 Will the Software Work?
Not if you don’t use it. Let’s talk about why tools fail and how to make them work for you.
📌 Setting Up Your Software to Optimise Your Business Processes
The right setup = the right results. Why it all starts with your processes (and how to get them right).
👉 You can read these in any order, but they flow best as listed above!