An epic is a massive user story that cannot be completed in a sprint. This high-level narrative is frequently divided into smaller ones that may be finished in a sprint. An epic, in any form, may be used to plan ahead and arrange your work over several sprints. As you can see, an epic has very similar functions to a project. You should use an epic when you need to plan or organize your work across multiple iterations or projects. You would use a project when you need to manage the completion of a single iteration or release. It is important not to confuse an epic with a sprint; you cannot complete an epic in a single sprint. Epics are commonly used by large organizations where multiple teams are working on different parts of one overall product. This allows everyone to see what part they are working on and how it fits into the bigger picture. Epics also help managers understand the scope of their team's work so that resources can be allocated accordingly. Large organizations may have hundreds or even thousands of epics. This is because each epic typically contains many stories that can be completed within a single sprint. For example, an epic for a messaging app might include items such as "Send message", "View messages", "Create folders", and "Delete messages". Each item in the epic is considered its own story for the purposes of planning and management.