User stories
Hello
When articulating requirements, should User Stories come first before identifying what's needed to be done? That is, should user stories be the first thing we talk about when talking about requirements?
A User Story is a good starting point for talking about requirements with users. They are often written in the language of the users, so it becomes easy to talk to stakeholders. to work through the needs, build up different flows, and then design and implement. But Scrum does not require User Stories or any particular format for Product Backlog Items. Some PBIs may be expressed well as User Stories, others may not be. You can use the appropriate representations for the PBIs that help the team understand what is needed to decompose, estimate, and execute the work needed to realize the requirement.
When articulating requirements, should User Stories come first before identifying what's needed to be done? That is, should user stories be the first thing we talk about when talking about requirements?
Could a User Story be a means through which a possible requirement is talked about?