An Epic is a new, one-time, initiative that results in a significant improvement for the Customer or the Company. Every team should have at least one Epic, but not more than two Epics, running at any given point in time.
The life cycle of an epic begins with a Product Owner defining a Product Concept Go / No Go and reviewing it with the Chief Product Officer. If the two of them agree that the epic is worth pursuing they will then solicit the feedback of at least another two Product Owners and once consensus is reached between all parties they will then publish the Product Concept Go / No Go to the Metascrum for review. If the MetaScrum agrees to the Epic the Product Owner then defines how the Epic will be launched as per the Business Review which is brought back to the Meta-Scrum to get consensus and coordination across all teams as to what is required to complete the launch. Once shipped the Product Owner confirms with the Meta-Scrum that all work as defined in the Business Review is complete and the Product Owner sets when the Measure of Success for the Epic will be validated. On the validation date the Product Owner completes the validation and presents the conclusions to the Meta-Scrum.
The elements of what should, if applicable, be included with each of the stages of an Epic;
- Product Concept Go / No Go
- Business Review Go / No Go
- Launch Review
are defined here.