Doubt about having control TFS version

Question

I am learning versioning, my doubt is with respect to the terms shown in the figure below Epic and Issue, looking for their translation for me did not make sense how to use these options to create a Work Item

Answer 1

According to microsoft document, Epic is a general item that is above Features. It’s a general definition of a problem, it’s something that transcends a release or project interaction. It is a concept used by the Agile methodology.

Issue is a deterrent for the progress of the project. It is not an error, but it is something that needs to be solved in order for the project to be correct. The resolution goes through an investigation. The outcome of this investigation may generate a bug or other necessary action, or may be dispensed with as something not relevant and may be recorded only as historical.

This is usually used in the CMMI methodology.

Answer 2

Work Items are not for source code management but for requirements management.

Team Foundation Server (TFS) is a very complete ALM tool, it is not only a source code versioner, but also includes requirements management, build, deploy module, etc... All of them are under a platform, which is what the TFS ends up being, instead of several tools attending the various disciplines of ALM, a single and with integrated security administration and management, thus facilitating in the administration.

By being delivered, Work Items can be related to checkin a code, if you’re using TFVC, or commit, if you use Git. And with that you have code history related to the requirements.

A Work Item is the abstraction of requirements, so it can be of type Issue or Epic, each with its function within software development.