Kanban system for managing the flow of Epics.

Epics being the units of information for capturing large software needs in a way that encourages easier collective prioritisation.

This concept is an adaption of the SAFe portfolio Kanban system [1] with an emphasis on the Epic as a unit of information over what underlying portfolio of value streams the Kanban system represents.

Unlike with implementing SAFe, this Kanban system concept does not require a change to team structure and team practices (other than team practices associated with communicating and prioritising large needs). This adaptation intentionally stayed close to SAFe, and it should be straightforward for a SAFe practitioner to relate an Epic Kanban system to a SAFe Portfolio, ART, or Solution Train Kanban system, e.g. as part of transitioning into implementing a SAFe configuration [1].

For experience report explaining the motivation for introducing this customised SAFe concept see here.

[1] Scaled Agile, Inc. (2023). SAFe 6.0 for Lean Enterprises. Retrieved July 5, 2025, from https://framework.scaledagile.com/.

The Epic Kanban system has two parts to it: The Epic (unit of information) and Kanban system (how Epics flow). Hence the reason for two of the repos in this github area.