BA-201 · Question #10
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…
The correct answer is B. User stories. User stories are short, structured descriptions of a desired outcome written from the stakeholder's perspective, typically in the format: 'As a [role], I want [capability], so that [value].' They are explicitly designed to capture intended results without prescribing solutions…
Question
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?
Options
- ARequirements
- BUser stories
- CEpics
How the community answered
(40 responses)- A3% (1)
- B95% (38)
- C3% (1)
Explanation
User stories are short, structured descriptions of a desired outcome written from the stakeholder's perspective, typically in the format: 'As a [role], I want [capability], so that [value].' They are explicitly designed to capture intended results without prescribing solutions, avoid technical assumptions, and keep focus on stakeholder value. Requirements (Option A) tend to be more detailed, solution-oriented specifications that can introduce assumptions about implementation. Epics (Option C) are large bodies of work that group multiple user stories-they are too broad to 'clearly define' specific intended results for planning purposes. User stories are the Agile standard for expressing stakeholder value at the right level of granularity for development and implementation teams.
Topics
Community Discussion
No community discussion yet for this question.