PMP · Question #387
A new project manager is planning an information security project for a company that resides in different countries. What is the first step the project manager should take to gather customer…
The correct answer is A. Conduct a stakeholder analysis to identify how regional policies may influence needs. For an international information security project, the project manager's first step to gather customer requirements should be to conduct a stakeholder analysis to identify how regional policies influence needs.
Question
A new project manager is planning an information security project for a company that resides in different countries. What is the first step the project manager should take to gather customer requirements?
Options
- AConduct a stakeholder analysis to identify how regional policies may influence needs
- BRequest relevant stakeholders to conduct an analysis and reach consensus independently
- CConduct a project scope review workshop with relevant stakeholders
- DConduct project planning meetings in one location with relevant stakeholders
How the community answered
(22 responses)- A77% (17)
- B14% (3)
- C5% (1)
- D5% (1)
Why each option
For an international information security project, the project manager's first step to gather customer requirements should be to conduct a stakeholder analysis to identify how regional policies influence needs.
For an international information security project, understanding the diverse regional policies, regulations, and specific needs of different stakeholders through a comprehensive stakeholder analysis is the foundational first step. This ensures that all relevant requirements, especially those influenced by geographical and legal factors, are identified from the outset.
Requesting stakeholders to analyze and reach consensus independently is not the project manager's role in initiating requirements gathering; the PM needs to facilitate and guide this process.
A scope review workshop is premature before identifying and understanding the relevant stakeholders and their unique regional specificities and influences.
Conducting meetings in one location might not be feasible or inclusive for an international project, and it's a method for gathering, not the absolute first step of *identifying* what needs to be gathered.
Concept tested: Stakeholder analysis and international project planning
Source: https://learn.microsoft.com/en-us/dynamics365/project-operations/prod-cons/project-planning/stakeholder-management
Topics
Community Discussion
5A. My mentor always says before you gather requirements across multiple countries you need to know who your stakeholders are and what regional policies shape their needs, so stakeholder analysis comes first. C and D skip that groundwork and jump straight to meetings without understanding the landscape.
A wins, stakeholder analysis comes first. C is tempting but premature.
Agree on A but heads up, the exam usually frames it as identifying stakeholders rather than analyzing them, so watch for that wording distinction or you will second guess yourself.
A is the answer PMI wants. You have to know who your stakeholders are and how their regional regulations shape requirements before you can gather anything useful. C is tempting because a scope review workshop sounds productive, but you can't run that workshop effectively without first identifying the stakeholders and understanding their regional constraints. D is a trap because flying everyone to one location ignores the logistical and compliance realities of a multi-country project.
Saw this last Tuesday, A is right because you need to ID stakeholders first before anything else.