A company wants to develop a product roadmap to guide future development efforts. The product owner asks a business analyst (BA) to lead the analysis effort.
Feature suggestions have been compiled from customer support calls. Which of the following should the BA do first?
The first step for the business analyst should be to confirm the feature requests. This involves validating that the suggestions gathered from customer support calls are accurate, relevant, and align with the product vision and strategy. Only after confirming the validity of the feature requests can the BA proceed to determine their value, compare implementation costs, or prioritize them in the backlog. This ensures that the subsequent steps are based on accurate and reliable information.
This is E&C KA. Conduct elicitation then confirm elicitation. The answer is D
The correct answer is A. Feature suggestions have been compiled from customer support calls. What's the need of reconfirming considering the source of information (support calls). Look at it from a practical point. I believe determining the value of the features is the logical thing to do next. Its not a BABOK question.
I think the answer should be C. confirm the feature requests (requirements)
I think you meant D...
Ans is C- features can be prioritized in different ways including value but not necessarily only by it. there can be a regulatory requirement which may produce low value but has to be done first. Hence Prioritisation is step no 1.
Confirm elicitation
The answer is A, you can only prioritize when you have placed a value on something.
I am thinking this should either be C or D. Leaning toward C since it roughly translates to "5.3 Prioritize Requirements" and D roughly translates to "7.2 Verify Requirements"
Leaning toward C since it roughly translates to "5.3 Prioritize Requirements" - The purpose of Prioritize Requirements is to rank requirements in the order of relative importance. Prioritization is the act of ranking requirements to determine their relative importance to stakeholders. When a requirement is prioritized, it is given greater or lesser priority. Priority can refer to the relative value of a requirement, or to the sequence in which it will be implemented. Prioritization is an ongoing process, with priorities changing as the context changes. Inter-dependencies between requirements are identified and may be used as the basis for prioritization. Prioritization is a critical exercise that seeks to ensure the maximum value is achieved. and D roughly translates to "7.2 Verify Requirements- Verifying requirements ensures that the requirements and designs have been defined correctly. Requirements verification constitutes a check by the business analyst and key stakeholders to determine that the requirements and designs are ready for validation, and provides the information needed for further work to be performed.
Clear Ans D. These features elicited are unconfirmed and need to be confirm with other elicited results or against source information. Confirming elicitation results checks the information gather during an elicitation session for accuracy and consistency with other information.
A is the correct option. All features are customer suggestions and confirming such might be close to impossible.
"Before the BA can proceed with any analysis of the features, they need to confirm that the feature requests are valid and aligned with the product vision and goals. Customer support calls may not reflect the actual needs and preferences of the target market, and may include requests that are out of scope or inconsistent with the product strategy. Therefore, the BA should first validate the feature requests with the product owner and other stakeholders, and eliminate any irrelevant or invalid ones. BABOK Guide v3, section 7.2.2.1: “The business analyst validates that the requirements and designs are aligned with the business need and the solution scope."