CCBA · Question #5
Tracy is a business analyst for her organization and she's gathered and identified the needed requirements for the solution scope. What must Tracy do before she can begin managing the requirements? Ch
The correct answer is C. Tracy must identify roles, responsibilities, and owners of the requirements to fully manage the. Before managing the requirements, Tracy must identify the roles, responsibilities, and owners of the requirements, as this is one of the tasks under the business analysis planning and monitoring knowledge area1. This task involves defining who will be involved in the requirements
Question
Tracy is a business analyst for her organization and she's gathered and identified the needed requirements for the solution scope. What must Tracy do before she can begin managing the requirements? Choose the best answer.
Options
- ATracy must decompose the requirements in WBS.
- BTracy must create cost-benefits analysis of each requirement to manage the benefits first.
- CTracy must identify roles, responsibilities, and owners of the requirements to fully manage the
- DTracy must communicate the requirements to the stakeholders for their consent and approval.
How the community answered
(29 responses)- B3% (1)
- C93% (27)
- D3% (1)
Explanation
Before managing the requirements, Tracy must identify the roles, responsibilities, and owners of the requirements, as this is one of the tasks under the business analysis planning and monitoring knowledge area1. This task involves defining who will be involved in the requirements developmentand management process, what their roles and responsibilities are, and who has the authority to approve or change the requirements. This helps to ensure clarity, accountability, and collaboration among the stakeholders and the business analyst. The other options are not prerequisites for managing the requirements, but rather activities that may be performed during or after the requirements analysis and design definition knowledge area2. Decomposing the requirements in WBS (A) is a technique for breaking down the requirements into smaller and more manageable components. Creating cost-benefits analysis of each requirement (B) is a technique for evaluating the value and feasibility of the requirements. Communicating the requirements to the stakeholders for their consent and approval (D) is a task for verifying and validating the requirements.
Topics
Community Discussion
No community discussion yet for this question.