7
I recently started using Visual Studio Team Services, mainly for the availability of free Git private repositories.
After a while I realized that it has several resources to manage requirements and the work being accomplished. As I work alone, among the Scrum, Agile and CMMI models I chose Agile.
The resources I refer to are in the option "Work" and there we can mount a backlog, view a board on which 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. I happen to get really lost in organizing the requirements.
In general, when contacting the end user of the system to collect the requirements, what we get is a list with everything the user needs. At the moment I am working on a project in which the user sends me an e-mail list of system requirements.
Having this kind of list of requirements I need to organize there, but it’s been really complicated. First because there are several options: Features, epics, user Stories (I’ve even asked the meaning of this here), second because there is how to relate these things, associate user Stories to Features and etc.
Like any tool, if these backlog resources are misused it is clear that can end up generating more confusion than organization.
That’s why I want to know: how can a developer who works alone use these features of Visual Studio Online to have an organized backlog? How to take an informal list of requirements and organize in the backlog of Visual Studio Online in order to get the work organized and facilitate development?