Adopting an agile approach with epics
The concept of an epic refers to a large body of work that can be broken down into smaller stories, which Jira sometimes refers to as issues. Multiple teams can work together on multiple projects, and multiple boards can be used to track multiple epics at once. Usually, a set of sprints precedes an epic. The user stories of an epic will be added and removed as the team learns more about it through development and customer feedback. Essentially, agile epics adopt a flexible scope based on customer feedback and team cadence.
A good epic should provide all the resources a development team needs to succeed. As far as their work hierarchy is concerned, it is the top tier. While understanding how an epic fits into other agile structures is critical for directing the daily developer work, it also provides important context for evaluating epics.
The act of breaking down an epic into smaller pieces makes it easier to understand and maintain momentum...
