I've heard both about use cases (I'm talking about the description, not the diagram) and user stories being used to gather requirements and organize them better.I work alone, so I'm just trying to find the best way to organize requirements, to understand what has to be done in the development. I don't have, nor need, any formal methodologies with huge documents and so forth.User stories I've seem being used to build the product backlog, which contains everything that needs to be done in the development.Use cases, on the other hand, provide a description of how things are done in the system, the flow of interaction between external actors and the system.It seems to me that for one use case there are several user stories.This leads me to the following question: when discovering requirements, what should I do first? Find and write user stories or find and write use cases? Or they should be done at the same time somehow?I'm actually quite confused. Regarding use cases and user stories, for a developer who works alone, what is a good workflow, to use these methodologies correctly in order to have a better development?
Which should be done first: use cases or user stories?
agile;requirements;user story;use case