Epic (requirements management)
In the context of requirements management, an epic is the description of a requirement for new software on a high level of abstraction. The description of the requirement is done in everyday language (analogous to user stories ).
approach
In the so-called story breakdown , an epic is broken down into several user stories with the aim of better detailing. This process breaks down overview descriptions into detailed descriptions in order to facilitate implementation by the development team. Here, the description to get applications in addition to everyday language, even for visualizations. B. by UML diagrams, used.
The term "Epic" is mainly used in agile software development in requirements management . Epics are used to develop a product backlog as part of Scrum . They give the author the opportunity to first develop an aggregated overview of new product requirements without having to go into the details of a requirement. In this respect, epics cannot be implemented directly in software coding, but require the detailing, which is done under Scrum in the preparation of a sprint planning meeting. The epic is in contrast to the user story , which describes a requirement in a fine-grained manner and represents a detailing of the epic on a granularity level that can be implemented in software code.