I’m a big fan of Dean Leffingwell and his work on the Scaled Agile Framework (SAFe). He’s been bringing lean thinking to software development for some time now. I work in a massive IT organization that has identified SAFe as how we’d like to develop software going forward.
Listen for these key concepts in the video below.
- The Customer and the Value Stream are key to the framework
- Value streams are the central organizing construct for SAFe.
- SAFe as a model, organizes around value, and this helps speed delivery
- Funding value streams vs. funding Agile Release Trains (ARTs)
- When Requirements are needed vs. the concept of Solution Intent
- General purpose solutions vs. ‘bespoke’ solutions
Over the past few years, I have heard many software development professionals say things like, “It’s a pretty good concept, but it doesn’t work in the real world.” or “SAFe doesn’t account for Architecture or other enablers.”
If you are in IT, you owe it to yourself to get up to speed not just on SAFe, but on the underlying lean thinking concepts that are driving it. If you don’t, you risk getting left behind both organizationally, and in your IT career.
Bob H – April 28, 2017
Scaled Agile Framework home: http://www.scaledagileframework.com/
Lean-Agile Mindset Abstract: http://www.scaledagileframework.com/lean-agile-mindset/
Value Streams Abstract: http://www.scaledagileframework.com/value-streams/
Team Kanban Abstract: http://www.scaledagileframework.com/team-kanban/
This week I had the opportunity to meet and hear Dean Leffingwell talk on Scaled Agile Framework (SAFe) and its history. It was fascinating to hear him recount the early days of Agile, and how the SAFe came into existence. What impressed me most was how he continually tied Agile and SAFe back to the teachings of Taiichi Ohno, W. Edwards Deming, and to the Lean concepts underpinning Agile. I am a late arrival on the software development scene, and I was working to improve First Call Resolution in an airline call center while people like Dean, Al Shalloway, and Mary and Tom Poppendieck were figuring out how to apply Jim Womack’s “lean thinking” to software development. It was a great presentation and while I have many more questions than answers, I am sold on the concept that Agile can scale effectively.
The Scaled Agile Framework (SAFe) is a proven knowledge base for implementing agile practices at enterprise scale. SAFe’s primary user interface is a “Big Picture” graphic (http://scaledagileframework.com/) which highlights the individual roles, teams, activities and artifacts necessary to scale agile from the team, to teams of teams, to the enterprise level. (The image at the top right is literally just one corner.) If you are serious about process improvement in the IT space, I strongly recommend you check this out.
Bob Hubbard, July 2013
The Scaled Agile Framework is a proven knowledge base for implementing agile practices at enterprise scale. Its primary user interface is a “Big Picture” graphic which highlights the individual roles, teams, activities and artifacts necessary to scale agile from the team, to teams of teams, to the enterprise level.
The Big Picture describes three levels of scale:
Team, Program and Portfolio. Each of these scales the essential agile elements of Value (requirements and backlogs) Teams (from development team through portfolio) and Timebox (iteration, PSI, budget cycle). This model of agile adoption has been elaborated primarily in Dean Leffingwell’s books Agile Software Requirements: Lean Requirements for Teams Programs and the Enterprise (2011) and Scaling Software Agility: Best Practices for Large Enterprises, (2007) and his scalingsoftwareagility blog.
Leffingwell, Dean (2011).
Agile Software Requirements, Lean Requirements Practices for Teams, Programs, and the Enterprise,
Addison-Wesley Professional, ISBN 978-0321635846.
Leffingwell, Dean (2007).
Scaling Software Agility, Best Practices for Large Enterprises,
Addison-Wesley Professional, ISBN 978-0321458193.