Difference between epics and features

I'll explain how you understand the code, even if it does not have a direct relationship between the terms:

Think of epic as namespace , feature as a class, and story as method. Why in every development has a module that has objects that have behaviors.

So is a general description of what you want from the software. There are not many details and it is recommended to keep in just one interaction. It is a way to organize (group) many features . An example is managing products.

feature is something a bit more concrete than it will be, it has a little detail of what that is, its function. In case it is complex it must also keep within a development interaction. As an example we can mention inserting the engineering of the product or the sale of the product.

Stories tells what to do, what operations the user will do on top of that feature . Examples can be: seller issues sales order, financial approves sale, stockist separates products, dispatcher issues tax invoice.

Obviously a story can use a feature inside it, just as features may have other characteristics. Eventually a feature need not have stories. The epic is interesting in more complex systems. It's unusual but a story may not be part of a feature.

So epic has nothing to do with size * but rather with greatness, which are different things. Epic is at a level above summarization. It's like a country. There are smaller countries than states and municipalities, so size does not matter, but the scope of it does.

This is all part of the requirements analysis. If it does wrong, and everyone else does, development gets complicated.

Epic, Features and User Stories are SCRUM artifacts, not VSTS definitions.

These artifacts help you break the values of your deliveries into blocks of expectations.

In a very simple example, a simple store system:

• Epic 1: Logistics
  • Feature 1: Inventory Items
    • Story 1: As user resposable by stock, I want to list items that are in stock;
    • Story 2: As a package reception agent, I wish to be able to inform you that new products arrived in stock
  • Feature 2: Invoices
    • Story 1: As an accounting user, I want to post NFs on the system;
• Epic 2: Online Shop
  • Feature 1: Display
    • Story 1: As a customer, I'd like to filter for products on promotion
    • Story 2: As a customer, I want to add an item to the shopping cart
  • Feature 2: Issue Purchase Order
    • Story 1: As a customer, I want to create a purchase order
• Epic 2: Finances
  • Feature 1: Purchase Order Audit

So you can break your project by the size of delivery values.

You can see more on SCRUM Guidance in Brazilian Portuguese