for solution developments in which the requirements in general and the extensive investments within a portfolio are recorded. Due to the scope of information and their impact, Epics must have the minimum viable products (MVP) defined and
secured by Lean Portfolio Management
(LPM) before they areimplemented. As for the portfolio, corresponding Epics are cross-functional and include multiple value streams and program increments
(PI).Epics are divided into business Epics and enabler
Epics.Business Epics directly deliver business value, while Enabler Epics are used to advance the Architectural Runway to support upcoming business or technical requirements. In addition, Agile Release Trains
(ART) develop and deliver Epics following the Lean Startup cycle. Epics are important business investments and require stakeholders to agree on their intent and definition. Before Epics are deployed, they must be reviewed, analyzed, approved or rejected. The review is usually done using the highest Weighted Shortest Job First (WSJF). Portfolio Epic owners are responsible for the critical collaboration required for the task at hand. The situation is different for enabler epics, which are managed by enterprise architects.