CBAP · Question #315
There are four inputs to the manage solution scope and requirements process. Which one of the following is not an input to the manage solution scope and requirements process?
The correct answer is C. Requirements [Approved]. Requirements [Approved] is an output of the approve requirements process and is not one of the four inputs to the manage solution scope and requirements process.
Question
There are four inputs to the manage solution scope and requirements process. Which one of the following is not an input to the manage solution scope and requirements process?
Options
- ARequirements Management Plan
- BStakeholder List, Roles, and Responsibilities
- CRequirements [Approved]
- DSolution Scope
How the community answered
(24 responses)- A4% (1)
- B4% (1)
- C75% (18)
- D17% (4)
Why each option
Requirements [Approved] is an output of the approve requirements process and is not one of the four inputs to the manage solution scope and requirements process.
Requirements Management Plan is a valid input that governs how changes to requirements and scope will be handled throughout the effort.
Stakeholder List, Roles, and Responsibilities is a valid input that identifies who has authority and interest in scope and requirements decisions.
Requirements [Approved] is produced by the approve requirements process and represents formally accepted requirements - it is a downstream artifact, not a precondition for managing solution scope and requirements. The four actual inputs to this process are Requirements Management Plan, Stakeholder List/Roles/Responsibilities, Solution Scope, and Requirements [Prioritized and Approved].
Solution Scope is a valid input that defines the boundaries of the solution and serves as the baseline against which scope changes are evaluated.
Concept tested: Inputs to the manage solution scope and requirements process
Source: https://www.iiba.org/standards-and-resources/babok/
Topics
Community Discussion
No community discussion yet for this question.