PMP · Question #359
A client is structured as a matrix organization for an agile project. The project manager is working on-site with key stakeholders from different parts of the organization. How should the project mana
The correct answer is B. Because there are different perspectives, perform a stakeholder analysis and act based on the. In a matrix organization with diverse stakeholders on an agile project, the project manager must conduct a stakeholder analysis to understand varied perspectives and determine appropriate engagement strategies.
Question
A client is structured as a matrix organization for an agile project. The project manager is working on-site with key stakeholders from different parts of the organization. How should the project manager handle the different stakeholders?
Options
- AAll stakeholders are important, so the project manager should follow directions provided by
- BBecause there are different perspectives, perform a stakeholder analysis and act based on the
- CThe project manager is working on the client's premises, so follow the directions of all the key
- DThis is an agile project, so listen only to the directions of the project manager's supervisor and the
How the community answered
(53 responses)- A4% (2)
- B81% (43)
- C4% (2)
- D11% (6)
Why each option
In a matrix organization with diverse stakeholders on an agile project, the project manager must conduct a stakeholder analysis to understand varied perspectives and determine appropriate engagement strategies.
Blindly following all directions from all stakeholders without analysis can lead to conflicting priorities, scope creep, and an inability to deliver a coherent product, especially in a matrix structure.
A stakeholder analysis is crucial in a matrix organization with diverse stakeholders because it identifies their interests, influence, and potential impact on the project, enabling the project manager to tailor communication and engagement strategies effectively. This analysis helps in prioritizing and managing conflicting demands from different organizational silos.
Simply because the project manager is on-site does not mean all key stakeholders' directions should be followed equally; their influence and interest still need to be assessed.
Limiting input only to the project manager's supervisor and product owner in an agile project with a matrix structure ignores the value of broader stakeholder engagement and feedback necessary for successful delivery.
Concept tested: Stakeholder analysis in matrix organizations
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/stakeholder-management
Topics
Community Discussion
5Confirmed B on my exam last month. Matrix orgs mean competing priorities, so doing a stakeholder analysis is the only way to figure out who has influence and how to engage everyone instead of just blindly following directions.
B is the right call here. I had almost this exact scenario on my exam last spring and the key was recognizing that matrix means competing perspectives, so stakeholder analysis is how you make sense of who influences what rather than just following everyone directions or picking one boss.
Leaned toward C first since being on-site at the client's premises makes it seem like you should just follow their directions. But matrix orgs mean competing priorities and multiple bosses pulling you in different directions, so B is the only real answer because you have to figure out who actually matters and what they want before you act on anything.
Going with C. When you're embedded on-site with the client in a matrix structure, the people who control resources and priorities are sitting right there, and aligning with their directions is how you actually keep work moving instead of getting stuck in analysis paralysis.
B is the right call here. In a matrix structure the PM rarely has direct authority over resources, so the play is to use influence, negotiation, and relationship-building rather than just deferring to whoever is sitting nearby.