ISEB-PM1 · Question #331
Which of the following is an input to Collect Requirements?
The correct answer is A. Stakeholder register. Stakeholder Register is an input to Collect Requirements because you need to know who your stakeholders are before you can solicit requirements from them. It identifies stakeholders' roles, interests, and involvement levels, which directly guides how and from whom requirements…
Question
Which of the following is an input to Collect Requirements?
Options
- AStakeholder register
- BRequirements documentation
- CPrototypes
- DOrganizational process assets
How the community answered
(23 responses)- A83% (19)
- B4% (1)
- C4% (1)
- D9% (2)
Explanation
Stakeholder Register is an input to Collect Requirements because you need to know who your stakeholders are before you can solicit requirements from them. It identifies stakeholders' roles, interests, and involvement levels, which directly guides how and from whom requirements are collected.
- B (Requirements documentation) is an output of Collect Requirements, not an input - it's what you produce during this process, not what you start with.
- C (Prototypes) is a tool and technique used within Collect Requirements to elicit feedback, not an input that feeds into the process.
- D (Organizational process assets) is a common distractor because OPA appears as an input to many processes, but in the context of this question (aligned with PMBOK 5th edition), it is not listed as an input to Collect Requirements.
Memory tip: Think "Who do I ask?" before you collect anything. The Stakeholder Register answers that question, making it the logical prerequisite input. Outputs (like requirements documentation) come after the work is done - if it sounds like a deliverable, it's probably an output, not an input.
Topics
Community Discussion
No community discussion yet for this question.