A Practical Guide to Untangling the Roles Behind Modern Project Delivery
Let’s set the scene:
You walk into the kitchen of a busy restaurant. Pans clanging, orders flying, steam rising. Someone’s barking updates, someone else is plating the risotto like it’s a sacred ritual, and someone’s fending off the owner who “just wants to add one more special to the menu tonight.”
Now ask yourself:
Who’s in charge?
The Chef? The Manager? The guy who just said, “This was supposed to be a soft launch?”
Welcome to the world of project delivery.
Where Scrum Masters, Agile Project Managers, and Traditional PMs often share the kitchen — and the chaos.
Let’s untangle their roles using this very relatable metaphor:
🍽 The Project = The Meal
👨🍳 The Team = The Kitchen Staff
🧾 The Stakeholders = The Hungry, Often Confused Diners
And our three stars:
- Traditional Project Manager = The Restaurant Manager
- Scrum Master = The Sous-Chef & Culture Keeper
- Agile Project Manager = The Hybrid Head Chef with a Spreadsheet
🥦 So… What Is an Agile Project Manager?
First off — yes, we know.
According to the Agile Manifesto, “Project Manager” isn’t a thing. It’s like saying “Agile Waterfall.” But let’s talk reality, not religion.
In the real world — especially outside software-native companies — Agile Project Managers exist because someone still needs to juggle timelines, budgets, vendor contracts, and that one executive who keeps asking if we’re ‘done yet.’
Here’s what an Agile PM really does:
- Coordinates multiple Agile teams without turning it into command-and-control theater
- Manages dependencies across sprints, teams, and functions
- Handles budgets, contracts, roadmaps (you know, grown-up stuff)
- Builds trust with stakeholders while protecting team autonomy
- Translates between Businessese and Techlish, in real-time
They’re part delivery lead, part facilitator, part shield, part politician.
💡 Think: Agile PM = Head Chef who respects the menu but still keeps the lights on and suppliers paid.
🔍 Agile PM vs Traditional PM: Same Species, Different Diets
Let’s compare the two managers in our metaphorical kitchen:
A Traditional PM builds the meal with a fixed recipe and expects every cook to follow it to the letter.
An Agile PM walks in with ingredients, a goal, and a team of specialists — and trusts the team to cook.
But they still have to report to the owner, remember the dinner service timeline, and restock the pantry.
👀 Agile PM vs Scrum Master: Stop Comparing Apples and Sous-Chefs
Here’s the part where people get spicy.
“Why do we need both? Aren’t Scrum Masters and Agile PMs the same?”
Not even close. Different knives. Different jobs.
The Scrum Master is the sous-chef: they keep the team focused, clear, and unblocked.
The Agile PM is the head chef: they ensure the dishes get to the table on time without compromising quality — or burning out the crew.
👉 One nurtures the team’s internal flow.
👉 The other navigates the external chaos.
🧂 But in Real Life? It’s Messy.
Let’s talk about the mess behind the magic.
Most orgs don’t run “by the book.” Agile PMs often become Scrum Masters. Or vice versa.
Sometimes, the Traditional PM is told to “go Agile” without support, training, or backup — and is expected to do both roles with none of the respect.
🚨 Warning signs you’ve got role confusion:
- The “Agile PM” is assigning tasks and calling it empowerment
- The Scrum Master is stuck making slide decks for leadership
- The Traditional PM is micromanaging sprint burndown
And everyone’s secretly dreaming of a sabbatical in Bali.
🍝 So Who Should Be Running Your Kitchen?
Ask yourself:
- Do we need someone to own the roadmap across multiple Agile teams?
→ You need an Agile PM. - Do we need someone to coach the team, run ceremonies, and unblock delivery?
→ That’s a Scrum Master. - Are we running a non-Agile project with fixed scope and a tight client contract?
→ Classic Traditional PM all the way.
🎯 Pro Tip: If you expect one person to do all three?
You’re not looking for a unicorn.
You’re looking for a burnout story in the making.
🧁 Final Thoughts: Let People Cook
Great delivery doesn’t come from rigid job titles.
It comes from knowing who’s doing what — and why.
Whether you’re an Agile PM coordinating across chaos, a Scrum Master holding space for team growth, or a Traditional PM navigating client expectations…
🧠 The secret sauce is clarity of roles, collaboration over control, and humility over heroism.
So next time you walk into your project kitchen, ask:
- Who’s the chef?
- Who’s plating?
- And who’s sneaking pineapple into the lasagna?
Because knowing the answer might just save your next delivery from going up in flames.
🔥If you liked this article, check out the next one where we walk through everything you need to know about Scrum artifacts.
Written by
Simina F.
| howtobecomeapm.com – Author
|