Building High Assurance Systems with SAFe 4.0.
Some of you already know that one of my technical pursuits over the last few years has been to better understand and describe the way in which enterprises can apply Agile methods to building big and important systems, specifically “high assurance” systems that have an unacceptably high social or economic cost of failure. We see these systems in our everyday lives—automotive and aeronautic systems, defense systems, medical devices, systems that control our financial security.
In much of my first career, I worked primarily in the medical device industry, building computer-based systems for healthcare. In that environment, a bug could have catastrophic consequences. Fortunately, to the best of my knowledge, I didn’t leave any such bugs in the field and I eventually moved on to other pursuits. But my interest in super high quality software has remained. Now, as Lean-Agile development crosses the chasm to the enterprise, it’s a good time to understand and rethink how these methods can accelerate quality, as well as speed. In support of this, we built some additional hooks into SAFe 4.0.
My talk this week at Agile2016 was on this topic. The packed room was a good barometer that this is fast becoming a new focal point for many in Agile development, so I’m sharing the slides below for everyone interested:
Anyone working with systems that are subject to regulation or industry compliance requirements, including Verification and Validation, should find this useful, especially if they are engaged in or considering a SAFe implementation.
I hope to turn this into a more detailed guidance article in the next few months, so your comments now on this topic are most welcome.