PMP Practice: Analyze stakeholders

Effective stakeholder engagement in agile projects requires understanding that different stakeholders have different information needs, preferred communication styles, and levels of desired involvement. By categorizing stakeholders based on their engagement needs and preferences, the project manager can design a targeted approach: marketing might attend sprint reviews to see working features, compliance might receive quarterly documentation reviews, end users might participate in usability testing sessions, and the executive sponsor might receive concise business value dashboards monthly. This tailored approach respects each stakeholder's time, provides them with relevant information in their preferred format, and maintains appropriate engagement levels without overwhelming anyone with unnecessary details or meetings. This is particularly important in agile environments where frequent communication is valued but must be purposeful and efficient.

**Why not A:** Using the product owner as the sole communication point creates a bottleneck and filters information through one person. Different stakeholders have different needs—the marketing director needs feature visibility, the compliance officer needs regulatory assurance, and users need feedback channels—and a single intermediary cannot serve all these needs effectively.

**Why not B:** Inviting all stakeholders to every sprint event wastes their time and overwhelms them with irrelevant details. The executive sponsor does not need to attend every sprint review, and the compliance officer does not need weekly visibility when quarterly assurance is sufficient. Over-communication drives disengagement.

**Why not C:** A single monthly report provides the same information to everyone regardless of their specific needs. The marketing director needs more frequent feature updates, while the executive sponsor wants high-level business value summaries. A uniform report either overloads some stakeholders or underwhelms others.