Hello All, In the most recent SAFe 5 update, we introduced operational value streams as first-class citizens of the SAFe Big Picture. Of course, they were always there, but as we evolve our approach to Business Agility, we also need to better identify our customers. This is especially important when the development value streams build systems that primarily support others within the company. In these cases, our customers are internal, and the systems we build.

Hi all.  Many of us work in organizations that are trying to improve product delivery where the solutions include hardware.  While SAFe offers software developers a myriad of practices to accelerate execution, we have had little to say to hardware developers. Until now. Today, the hardware community is in the same position as the software community was two decades ago when they experienced increasing business demand for faster and high-quality delivery.  The software community invented.

What do these things have in common? A lot more than you might think! During our SPC(T) class last week, SAFe Fellow and continuous-learning, deep-OCM-thinker Joe Vallone pointed our class to John Kotter and Holger Rathgeber’s latest fable, That’s Not How We Do It Here! The title alone piqued my interest and as a fan of their prior fable Our Iceberg is Melting  (I will always remember Penguin ‘NoNo’ in that book; and BTW if.

Hello Folks, The team thought it would be helpful to bring attention to a couple of the newest elements in SAFe. I got the first slot, to talk about the substantial changes to operational (this post) and development (next post) value streams in SAFe 5. Operational value streams (OVS) have been in SAFe for years, but they never been elevated to be an icon on the BP. Now they are. We tucked them up there.