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?
The user stories approach for requirements organization involves interviewing stakeholders and recording their stories as part of the requirements. User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, typically a user or customer of the system. This approach is user-centric and focuses on capturing specific scenarios or narratives to understand user needs and expectations.
babok 3. pg 360
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.
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.
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.
Requirements are always based on the objective and goals.