I hate that diagram. It looks like gibberish to anyone who hasn’t gone through a training to understand it, and even this it still looks like gibberish.
SAFe is about addressing the communication problems that happen as an organization grows. You’re looking at the diagram for everything that would be applied to a very large organization.
SAFe itself has a goal of using 50-150 person “release trains” that are essentially independent units. That’s the core of what’s going on.
Everything outside of that is about managing communication between other “trains”. In the diagram that you’re looking at, the bottom 2 sections where the CD Pipeline sits is where most developers will experience SAFe and you’ll find that it simply advocates for DevOps best practices.
I completely understand how everything else looks like a mess. It’s a lot to digest.
SAFe is about addressing the communication problems that happen as an organization grows. You’re looking at the diagram for everything that would be applied to a very large organization.
SAFe itself has a goal of using 50-150 person “release trains” that are essentially independent units. That’s the core of what’s going on.
Everything outside of that is about managing communication between other “trains”. In the diagram that you’re looking at, the bottom 2 sections where the CD Pipeline sits is where most developers will experience SAFe and you’ll find that it simply advocates for DevOps best practices.
I completely understand how everything else looks like a mess. It’s a lot to digest.