Epics, as you might imagine, are large stories. We want them to be able to be completed, so it's important that they have a distinct start and end, just like any story. We like to think of epics as something that would span multiple sprints, versus a story, which could be completed within a sprint. Epics are not groupings of work items, which is a common mistake that people make when organizing their work in the JIRA interface. We'll take a look at how to use components and labels to do this, instead of epics. Epics will contain stories, bugs, and tasks.
Stories are smaller than epics. Stories, bugs, and tasks are all on the same level hierarchically; they could all be prioritized against one another within our backlog to include in a sprint. Stories are also known as user stories, and they're called that because they...
