The standard format for writing user stories follows a specific structure: " As a [role], I want [goal] so that
[benefit]. " This format ensures that the user story captures who the user is, what they want to achieve, and why it is important.
* User Story Format :
* Role : The user role that is relevant to the story.
* Goal : The specific action or feature the user desires.
* Benefit : The reason why this feature or action is valuable to the user.
* Example Explanation :
* The correct example, " As an Investor, I want to see a summary of my investment accounts so that I can decide where to focus my attention, " perfectly fits the standard format. It specifies the user role (Investor), the goal (seeing a summary of accounts), and the benefit (deciding where to focus attention).
* Why Not Other Options? :
* A and D lack clarity on the benefit or the user ' s role, making them less effective as user stories.
* B is close but is more detailed than the standard format, making it less concise.
:
Appian Agile Practices Guide: Writing Effective User Stories
Using the standard format for user stories helps ensure that the development team clearly understands the user
' s needs and the value of the feature being requested.