Project Management

Please login or join to subscribe to this thread

Agile vs. Waterfall stakeholder management?

linkedin twitter facebook   Agile  
avatar
Anupam India
How is agile stakeholder management different than waterfall?
Sort By:
< 1 2 >
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Jun 25, 2019 3:37 PM
Replying to Mayte Mata Sivera
...
Each time that I read a question that starts by A vs W, I suffer a stroke. We should stop comparing both. The curiosity kill the cat, and I'm here!

I thing that most of us agree that there is no difference, however Rodrigo and Aaron opened a good topic, we can't forget that the organization and education of stakeholders are key.
Good to read that Mayte. Waterfall is a project life cycle. Agile is an approach that can be used with Waterfall life cycles.
avatar
Naji Shelala Professional Engineer and Certified Executive Coach| Coaching Talents Beirut, Lebanon
I see a bit of difference in this respect. This comes from the point of view that Change is accepted in Agile. Thus there is no much need in Agile to draw the influence Matrix of stakeholders, and No need to search for allies in Agile (unlike waterfall ).
In brief, the Change perspective makes the engagement of stakeholders unequal between the two approaches.
avatar
Thomas Walenta Global Project Economy Expert Hackenheim, Germany
Everything is connected.
Agile thinking sets boundaries that non-agile projects do not need to regard.

With agile comes a mindset, that is human centric and strives to collaborate, create positive relationships and outcomes. Self-organization requires less central or top-down power. Stakeholder engagement and influencing is achieved with soft techniques, 'managing without power' and building trust.
Besides the more technical life cycle considerations, this is the most characterizing attribute of agile.

Not necessarily is this the case with normal project management (and not all of normal project management is waterfall). Think military campaigns, layoff programs, Corona vaccinations or simple ERP rollouts. Think command and control, order and obey, just implement it (and you earn a shitstorm if you miss a milestone). Power exists in organizations, but the PM might not have it. With power come a lot more options regarding stakeholder engagement and influence.

So yes, they are quite different.
avatar
Paphatpisit Klinklan Regional Sourcing and Operation Manager| Krones (Thailand) Co., Ltd Samutprakan, Thailand
Jun 25, 2016 4:04 PM
Replying to Sergio Luis Conte
...
There is no difference.
YES. IT IS.
avatar
Piotr Lis Plano, Tx, United States
In General, there is no difference.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Far out in the uncharted backwaters of the unfashionable end of the Western Spiral arm of the galaxy lies a small unregarded yellow sun. Orbiting this at a distance of roughly 98 million miles is an utterly insignificant little blue-green planet whose ape-descended life forms are so amazingly primitive that they still think digital watches are a pretty neat idea..."

- Douglas Adams

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters