
There are two types of epics, each of which may occur at different levels of the Framework. Program and Large solution epics, which follow a similar pattern, are described briefly at the end of this article. This article primarily describes the definition, approval, and implementation of portfolio epics. SAFe recommends applying the Lean Startup build-measure-learn cycle for epics to accelerate the learning and development process, and to reduce risk. Portfolio epics are typically cross-cutting, typically spanning multiple value streams and Program Increments (PIs). Due to their considerable scope and impact, epics require the definition of a Minimum Viable Product (MVP) and approval by Lean Portfolio Management (LPM) before implementation. What if we found ourselves building something that nobody wanted? In that case what did it matter if we did it on time and on budget?Īn Epic is a container for a significant Solution development initiative that captures the more substantial investments that occur within a portfolio.
