Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
exam questions

Exam Certified Business Analyst All Questions

View all questions & answers for the Certified Business Analyst exam

Exam Certified Business Analyst topic 1 question 21 discussion

Actual exam question from Salesforce's Certified Business Analyst
Question #: 21
Topic #: 1
[All Certified Business Analyst Questions]

At the start of a new Agile development project, the Universal Containers product owner asked the business analyst (BA) to clearly define the intended results of the work based on stakeholder needs. The development and implementation teams will use the intended results to plan product decisions. The definition should avoid assumptions and focus on stakeholder value.
Which element should the BA choose to define the intended results?

  • A. Epics
  • B. Requirements
  • C. User stories
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Jude1337
Highly Voted 1 year, 7 months ago
"The definition should avoid assumptions and focus on stakeholder value." I guess because of this part of the questions answer "C" - user stories is correct.
upvoted 8 times
...
Neil231
Highly Voted 1 year, 8 months ago
Selected Answer: B
Requirements are used to define the intended results of the work and they should be based on stakeholder needs, be clear and specific, and avoid making assumptions. Requirements help the development and implementation teams to understand what needs to be delivered and how it should be tested. Epics and user stories are used to break down the requirements into smaller, more manageable pieces, but they are not typically used to define the intended results. - hence answer should be B. Requirements
upvoted 7 times
...
Nekan
Most Recent 10 months ago
Selected Answer: C
Development and Implementation teams work with User Stories, not Requirements. Even though User Stories have come from Requirements, the former i.e. User Stories speak directly to the needs of the stakeholders - whilst Requirements can focus on other things...Non-functional, General & Technical Requirements are all types of Requirements and sometimes are not directly focused on stakeholders.
upvoted 2 times
...
Melissa1994
1 year ago
Selected Answer: C
C because ' Should for on stakeholder value'.
upvoted 1 times
...
mchn83
1 year, 2 months ago
Selected Answer: C
C is correct
upvoted 2 times
...
aerodarius
1 year, 3 months ago
Selected Answer: C
User stories are a fundamental component of Agile development and are used to capture the intended functionality or features of a product from the perspective of the end-users or stakeholders. They are concise, specific, and written in a way that describes the user's need, the functionality they desire, and the value it provides. User stories help the development and implementation teams understand the requirements and objectives of the project, enabling them to plan product decisions that align with stakeholder needs and deliver the most value to the users. Epics, on the other hand, are larger, more high-level requirements that can be broken down into smaller user stories. Requirements is not a standard Agile term and doesn't align with the approach of defining user stories based on stakeholder needs and value.
upvoted 5 times
...
Alokv
1 year, 5 months ago
Answer is B. By defining clear requirements, the BA can articulate the intended results of the work in a way that is precise, measurable, and actionable.
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...