Scaled Agile Framework ~ Enterprise (SAFe) is quite an undertaking. I first started learning about SAFe back in 2017. At the time, I thought it as an extension of what I had learned over the years in Agile and Scrum. Having learned Lean Six Sigma a few years back, as it was capstone of my first exposure to it as a Yellow-belt in 2004. I later hear about Lean Agile software development, but everyone I knew was still doing waterfall. So in 2015 I started learning a bit about Agile software development. Added Scrum to my list of many things I learned, or learned about in 2016. I guess I started with Project Management stuff in 2010 with my studies towards PMP, which finally got a writing, Project Management Basics
And now I am writing about it as my knowledge checker. By now you know I hear about something, study it for a while, do a few things with it, and finally write about it.
SAFe things First
A few of the first things is figuring out how it all fits together, and what you need to know And do. Like embracing a Lean-Agile Mindset. What is that?
Understanding the SAFe Principles. What are they?
Implementing Agile Release Trains. Yes, I have a engineers hat with a Western Pacific patch on it. But more importantly I actually do have train-engineer striped overalls from Oshkosh.
I think the biggest hurdle for some companies other than getting their people on board is PI Planning. Maybe the biggest program is really vocabulary. Like SAFe stands for Scaled Agile Framework ~ Enterprise, and PI Planning is about Program Increment.
Another big hurdle revolves around Value. Value is a big deal to Lean folks, and should be to you as well. Finding value, executing and releasing value, defining value, and the list seems to go on.
But then you come to the building the Agile Portfolio.
How does Kaizen fit in? Kanban? and Waste?
In a nutshell those are the main talking points of Scaled Agile Framework ~ Enterprise (SAFe). Shall we dig in deeper?