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

Unlimited Access

Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.

Exam CBAP topic 1 question 64 discussion

Actual exam question from IIBA's CBAP
Question #: 64
Topic #: 1
[All CBAP Questions]

You are the business analyst for your organization. You are currently working with Steve on the organize requirements process. You and Steve have elected to use the user stories approach for this process.
What is the user stories approach for requirements organization?

  • A. Stakeholders' experiences equate to the stakeholder requirements.
  • B. Stakeholders are interviewed and their experiences are recorded to help identify the requirements.
  • C. Stakeholders' objectives are described to identify the requirements that the solution will need to support.
  • D. Stakeholders are interviewed and their stories are recorded as part of the requirements.
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
Dmylitos
1 month, 1 week ago
Selected Answer: D
Option C describes a different approach known as "stakeholder objectives." In this approach, stakeholders' overarching objectives or goals are identified to derive the requirements that the solution must support. While it's a valid approach, it's not specifically the user stories approach. User stories, as described in option D, focus on capturing specific user scenarios or narratives to express requirements in a more user-centric and narrative format.
upvoted 1 times
...
Rabbitsfoot
1 month, 3 weeks ago
Selected Answer: D
I'm going with D. Stakeholders are interviewed and their stories are recorded as part of the requirements. It aligns with the description of the user stories approach as outlined in10.48 BABOK V3. In the user stories approach, stakeholders' needs are captured through conversations or interviews, and their stories are recorded to define features of value to them. These recorded stories serve as the basis for identifying, prioritizing, estimating, and planning solutions. Therefore, option D accurately reflects the user stories approach for requirements organization.
upvoted 1 times
...
rmr29
7 months, 2 weeks ago
Conversation 10.48. User stories help teams to explore and understand the feature described in the story and the value it will deliver to the stakeholder. The story itself doesn't capture everything there is to know about the stakeholder need and the information in the story is supplemented by further modelling as the story is delivered.
upvoted 2 times
...
Dillon91
1 year, 6 months ago
babok 3. pg 360
upvoted 3 times
...
MFZZ
2 years, 3 months ago
Requirements are always based on the objective and goals.
upvoted 1 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 ...