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.
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.
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.
Requirements are always based on the objective and goals.
The correct answer is C. Stakeholders' objectives are described to identify the requirements that the solution will need to support. The user stories approach focuses on capturing stakeholders' objectives and goals to define the requirements for the solution. It emphasizes understanding what stakeholders aim to achieve and ensures that the solution aligns with their needs. This method is widely used in Agile frameworks, where user stories are written from the perspective of the end user to describe desired outcomes rather than technical details.
10.48.2 Description User stories capture the needs of a specific stakeholder and enable teams to define features of value to a stakeholder using short, simple documentation. They can serve as a basis for identifying needs and allow for the prioritizing, estimating, and planning of solutions. A user story is typically a sentence or two that describes who has the need addressed by the story, the goal the user is trying to accomplish, and any additional information that may be critical to understanding the scope of the story. With a focus on stakeholder value, user stories invite exploration of the requirements by promoting additional conversations with stakeholders and grouping functional requirements for delivery.