This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.
Is it Good to be SAFe?
A few weeks ago, I attended a Scaled Agile Framework Certification course taught by Dean Leffingwell. The course reinforced many of the concepts in Dean’s latest book, Agile Software Requirements, and was a good way for me to assess my understanding of agile at scale. I had several takeaways from the course, which to me means it was worth attending.
Over the next few weeks, I’ll be blogging (on our Product Blog) about how you can implement some key concepts in the framework using VersionOne’s Agile Portfolio Management (APM) capabilities.
**** August 2013 Update to include updated resources on SAFe****
Whitepaper on scaling enterprise agile: https://blog.versionone.com/wp-content/uploads/2013/02/14/enterprise-agile-white-paper/
Original article continued…
At the Agile2012 Conference, I spoke with many people about the Scaled Agile Framework (SAFe). Unsurprisingly, the opinions varied widely. Some organizations are finding great success implementing the framework. One of our customers shared with me that their organization was able to make a major change in their direction at a PSI (release) boundary, and having all teams synchronized on the same cadence was essential for making the change. Others cited that the Scaled Agile Framework was too heavyweight and was likely to be implemented with little understanding of the underlying principles that would be essential to long-term success.
Have you implemented SAFe? How is it working for you?