PMI-ACP practice question 18 of 35

Early in a project stakeholder analysis is performed: however, an organizational restructure redefines key roles What should the project team do?

Full set: 482 questions
Answer options
A: Note the changes to the restructure and roles that affect team activities
B: Use direct engagement and two-way conversation to update the stakeholder analysis for any new stakeholder requirements. Correct answer
C: Email a copy of the project vision to those redefined for key roles and ask if they need to be involved in the project
D: Obtain a copy of the redefined key roles to update the stakeholder analysis
Correct Answer:
B. Use direct engagement and two-way conversation to update the stakeholder analysis for any new stakeholder requirements.
Explanation

Agile principles prioritize individuals and interactions over processes and tools. When key stakeholders change due to a restructure, the most effective agile approach is to engage them directly. A two-way conversation is essential to understand their new perspectives, requirements, and expectations. This collaborative approach ensures the stakeholder analysis is not just updated with new titles, but with meaningful information that reflects the new reality, fostering alignment and buy-in from the start. Simply updating a document (D) or sending a one-way email (C) is insufficient and misses the opportunity for building relationships.

Why Incorrect

A. Noting changes is a passive action. Agile requires proactive engagement and communication to adapt to change effectively.
C. This is one-way communication and places the burden on the new stakeholders. It is not a collaborative or engaging approach.
D. This action is incomplete. While obtaining the new roles is necessary, it's a data-gathering step, not the engagement needed to understand new requirements.

References

1. Project Management Institute. (2017). Agile Practice Guide. Section 4.3.2, Engage Stakeholders, p. 52. "Agile methods promote a high degree of stakeholder engagement... This requires a collaborative approach to work through the details, which is best done via direct conversation."

2. Cohn, M. (2010). Succeeding with Agile: Software Development Using Scrum. Addison-Wesley Professional. Chapter 4, Roles, discusses the importance of continuous and direct communication between the team and stakeholders, especially the Product Owner, to ensure alignment.

3. Stray, V., & Moe, N. B. (2020). Understanding coordination in global software engineering: A mixed-methods study on the use of meetings and Slack. Journal of Systems and Software, 170, 110717. https://doi.org/10.1016/j.jss.2020.110717. This study highlights the importance of rich, synchronous communication (like conversations) for complex coordination and alignment, which is critical when stakeholder structures change.

Scroll to Top