CBAP · Question #358
A sports wristwatch product manufacturer wants to add a blood sugar monitoring toolkit to the watch. Market research has confirmed that the most profitable segment of the manufacturer's target custome
The correct answer is D. Requirements and design options are not detailed enough. When a solutions team cannot evaluate the merits of proposed approaches, it is because requirements and design options lack sufficient detail to support meaningful comparison.
Question
A sports wristwatch product manufacturer wants to add a blood sugar monitoring toolkit to the watch. Market research has confirmed that the most profitable segment of the manufacturer's target customer is looking for this feature. The business analyst (BA) worked with the product owner to finalize the set of requirements and design options and then defined multiple approaches for implementing the feature. At this point, the solutions' team agreed that they were unable to accurately assess the merits of each of the proposed solutions. What is the possible reason?
Options
- ARequirements are not allocated to solution components
- BToo many approaches are dividing the team
- CBusiness needs are unclear to the team
- DRequirements and design options are not detailed enough
How the community answered
(41 responses)- A12% (5)
- B2% (1)
- C7% (3)
- D78% (32)
Why each option
When a solutions team cannot evaluate the merits of proposed approaches, it is because requirements and design options lack sufficient detail to support meaningful comparison.
Allocating requirements to solution components is a step that occurs after a solution is selected, not a prerequisite for evaluating competing approaches.
Having multiple proposed approaches is normal in solution evaluation; the number of options does not itself prevent the team from assessing each one.
The scenario explicitly states that market research confirmed business needs and the product owner finalized requirements, so business needs are not unclear to the team.
Requirements and design options must be detailed enough for the team to assess technical feasibility, costs, risks, and trade-offs of each proposed solution. Without that level of detail, the team has no concrete basis for comparing approaches. The scenario confirms requirements were finalized but does not confirm they were specified in enough depth to support solution evaluation.
Concept tested: Solution evaluation readiness and requirements detail sufficiency
Topics
Community Discussion
No community discussion yet for this question.