Recently I started using Visual Studio Team Services, mainly because of the availability of private Git repositories for free.
After a while I realized that it has several features to manage requirements and the work being done. As I work alone, between the Scrum, Agile and CMMI models I chose Agile.
The resources I refer to are in the "Work" option and there we can set up a backlog, view a board where we can organize what there is to do, what is being done, etc.
The backlog, as far as I know, is where the requirements are organized. It turns out that I'm really lost in organizing the requirements.
In general, by contacting the system end user to collect the requirements, what we end up with is a list with everything the user needs. At the moment I'm even working on a project where the user e-mails me a list of system requirements.
Having this kind of requirements list I need to organize there, but it's really complicated. First of all, there are several options: features, epics, user stories (I even asked what this meant #
As with any tool, if these backlog features are misused, of course it may end up creating more confusion than an organization.
That's why I want to know: How can a developer who works alone use these Visual Studio Online features to have an organized backlog? How do I get an informal list of requirements and organize in the Visual Studio Online backlog in order to get the work organized and make it easier to develop?