User Story Role-Feature-Reason Template

Correct Answer: As a health-conscious user, I want a feature to track my daily caloric intake, so I can monitor and manage my diet effectively.

The correct answer follows the Role-Feature-Reason template explicitly and pertains closely to the basic requirement of tracking caloric intake without adding extra functionalities or deviating to a different solution. Wrong Answer 1 changes the method of tracking calories to scanning, which introduces an entirely new feature not mentioned in the scenario. Wrong Answer 2 extends the functionality beyond the basic requirement of tracking, including meal suggestions. Wrong Answer 3 shifts focus towards an alerting system based on deviations from a user's plan, which again is not the basic need expressed.

Correct Answer: 'As a Student, I want to comment on courses so that I can share my thoughts and feedback.'

The correct answer is 'As a Student, I want to comment on courses so that I can share my thoughts and feedback.' This statement formulates the requirement in the role-feature-reason format that is widely used in Agile methodologies. The role (Student), feature (comment on courses), and reason (share thoughts and feedback) are all clearly defined. The other answers fail at this. 'As a Course, I want to receive comments so that students can share their thoughts.' is incorrect because a course cannot actively want or do anything, it's not a role, it's a part of the software or a feature. 'As the Development Team, we want to build the Comment feature so students can leave feedback.' fails to use the user's perspective. The requirements should be based around the user's needs and wants, rather than what the development team wants to build. 'As a Scrum Master, I want the development team to create a Comment feature.' is not correct because it is the Scrum Master's desire, and not the user's need that is being expressed. The Scrum Master does not interact with the product in the same way the user or customer does.

Correct Answer: As a new user (Role), I want an optimized sign-up process (Feature) so that I can create an account faster (Reason)

The best answer is 'As a new user (Role), I want an optimized sign-up process (Feature) so that I can create an account faster (Reason)'. This answer best aligns with the Role-Feature-Reason framework for creating user stories. User stories are meant to be written from the perspective of the user (in this case, a 'new user'), detailing a feature they need (an 'optimized sign-up process') and explaining why they need it (to 'create an account faster'). The other answers are incorrect. 'As a developer, I want to optimize the sign-up process in order to enhance website UX', speaks from a developer's perspective, not a user. 'We need to optimize the sign-up process so it's easier for users', is vague about who is benefitting and why. Lastly, 'The sign-up process is too slow and requires optimization', does not mention a specific role, feature, or reason, so cannot count as a well-constructed user story.