In Visual Studio Team Services it is possible to organize the backlog in epics , features and user stories .
For each epic, an associated set of features can be defined, and for each feature an associated set of user stories can be defined .
What I do not understand is still the difference between epics and features . From what I've researched " epic is a very large requirement, which needs to be broken down into user stories ", but I do not understand the difference between this and features >.
Aliases, even this definition of epic is subjective, because after all, how do I know that something is big enough to be an epic ?
In this way, what really are epics , what really are features and what is the real difference between them?
Some examples I saw in a video on the internet:
Epic: Mobile strategy
- Feature: Mobile favoriting
Epic: Continuous improvement
- Feature: Botify the wordoo service
- Feature: Improve performance