SAFe: a collection of comments from leading experts

Image from BrownSafe.com Antique Vault Doors

This below is a collection of comments about SAFe from leading experts in Leadership, Management, Tech & Agile. This collection is periodically updated as new info become available. Feels free to copy and distribute this post as you please.

Al Shalloway, 2018-2019

Al Shalloway is a well-respected industry thought leader in Lean, Kanban, SAFe, Scrum and agile design. He is the author of several successful books, and the developer of the new FLEX framework. He is also a former SPCT, contributor and gold partner with SAFe.

He is indeed the last lean-agile thought leader to “ditch” SAFe (amicably break off the relationship with Scaled Agile Inc, no longer providing SAFe training). Al knows SAFe from the inside-out: he has been the first SAFe program consultant trainer outside Scaled Agile Inc. and has been a contributor to SAFe for six years.

After 6 years he decided to leave SAFe because, in his own words:

  • SAFe has grown considerably more complex than it needs to be
  • Many small- to mid-scale orgs (technology <1000 ppl) are looking to Essential SAFe even though is not a good solution for them
  • Many orgs are looking to take “SAFe out of the box” which has never been our approach
  • SAFe training is not tailored to the size of the organization that will use it

He recently added (June 2019) that he stopped being a SAFe SPCT after he was told that to renew his certification he had to do a few “by the book” SAFe adoptions. And we know that implementing agile “by the book” it is not agile at all.

His comments are congruent with other comments from other disillusioned SAFe professionals (see below for a good example) and with comments made by the other experts quoted below: SAFe is overly complex and requires tailoring down, and this basically means SAFe is fundamentally the opposite of the very essence of Agile.

Bob Galen, April 2019

Bob Galen is an Agile Methodologist, Practitioner since the late 90’s and Coach. He is the author of three agile centric books, a prolific blogger, and pod-caster.

He became SAFe SPC certified several years ago. He tried to understand, support, and apply it, but then he struggled with it for a long time to the point that he just can’t be associated with it any longer.

In his article SAFe no longer – my final farewell (that contains more links on the subject and very interesting comments) he mentions these reasons:

  • It’s too big, far from the principles of simplicity at the heart of agility.
  • It’s sold to leaders to control their organizations – a costly silver bullet.
  • It creates far too many roles, layers, flows, etc.
  • It’s too focused on certifications and training – a cash cow.
  • It’s created a community of SPC’s and other consultants who think being agile is about…SAFe. Who look at every agile context and think SAFe is the solution.
  • It’s created lazy organizations who think that the framework does the heavy lifting of transformation for them.

Several agile professionals that got SAFe certified are becoming disillusioned and are moving away from SAFe for similar reasons.

Steve Denning, 2015-2019

Steve Denning is a recognised expert and author in leadership, management, and innovation. These below are some excerpts about SAFe from one of his articles on Forbes: How To Make The Whole Organization Agile

“Equally, some of the current efforts to ‘scale Agile,’ such as the Scaled Agile Framework or SAFe, are counterproductive.”

“SAFe destroys the very essence of Agile.”

“Like the failed management fads of the 20th Century, it degrades and undermines everything in Agile that is authentic and useful.”

More recently he added about SAFe: “it gives the management a mandate to call themselves agile and keep doing what they have always done” and “My question would be: why would anyone with a genuine Agile mindset be using SAFe in the first place?” reaching to the conclusion that: “SAFe is the epitome of ‘fake Agile’.”

Ron Jeffries, 2014-2019

Ron Jeffries is a co-author and one of the 17 original signatories of the Agile Manifesto, and one of the creators of Extreme Programming. He published one of the most informed and well-presented critiques to SAFe here:

– Issues with SAFe: http://ronjeffries.com/xprog/articles/issues-with-safe/

– all Ron’s posts on SAFe: https://ronjeffries.com/categories/safe/

Ron Jeffries has the habit of updating his posts when things changes or new information become available. For this reason, his post can be considered actual even after the publishing date.

Andy Hunt, July 2019

Andy Huns is a programmer, publisher at The Pragmatic Programmers, and author of best-seller books on software development. He is also a co-author of the Agile Manifesto and founder of the Agile Alliance.

Asked for a comment about SAFe Andy here concludes that “SAFe is not an agile approach.” He also tells “I have friends who have made great careers thanks to SAFe — going in afterwards and cleaning up disastrous, failed adoptions.”

James Grenning, July 2019

James Grenning is the inventor of the Planning Poker agile practice used all around the world. He is a software development expert, both technical and managerial. He is the author of articles and a book on applying Agile to embedded software development. He is also a co-author of the Agile Manifesto.

He says here his knowledge about SAFe is limited, and so he forms his opinion based on the message of SAFe and how it is being adopted. Indeed, he says he has many SAFe friends out there.

In this post he takes a very pragmatic and non-judgmental view on SAFe with an interest in the engineering side:


While I suggest reading the original post (as well as for all the other links in this article) these are few excerpts that resonate with me:

<<Maybe improvement really has to start with the individual, and the team. One of the things I’ve really come to appreciate about extreme programming is how its practices lead to continuous improvement. >>

<<Looking at Essential SAFe, XP is mentioned. A lot of good things are mentioned. Though it concerns me that the SAFe Road map appears to get teams involved so late.>>

<<If SAFe is where you learn to do agile so you can figure out how to be agile, maybe it will help. I guess time will tell.>>

Brian Marick and Jon Kern, July 2019

Brian Marick is a programmer and software testing consultant. He is also a co-author of the Agile Manifesto and former chair of the Agile Alliance.

Jon Kern is an aerospace engineer-turned programmer, software architect, and team leader/coach with a focus on methodology and business value. He is also a co-author of the Agile Manifesto.

Brian asked for a comment about SAFe candidly says here “I don’t know enough about SAFe to have an opinion.”

Jon asked for the same comments says here that he want to witness a company doing SAFe before commenting.

The comments on SAFe collected here are indeed from people that speak out of their knowledge and experience and are not afraid to admit when they don’t know enough about a subject to comment on it.

Chris Matts, 2019

Chris Matts is an experienced Agile practitioner specialised in delivering trading and risk management systems in investment banks. He contributed to BDD with Daniel Terhorst-North (AKA Dan North), he developed Feature Injection practice and with Olav Maassen he introduced the concept of Real Options in Agile.

Chris highlights that the creators of SAFe have not engaged with the wider Agile community in the usual debate that challenges the new practices in a process that validates and improves them, and ultimately gives (or not) credibility. Chris adds that he is not aware of a single leader in the Agile Community that has endorsed SAFe.

Chris continues analysing and critiquing the SAFe definition and use of Epics.

These are the posts on SAFe by Chris:

The picture that emerges on SAFe practices, after I put together the comments from Chris and the comments of other leading experts on other SAFe practices, suggests to me that: SAFe practices accommodate the status quo of approaches from the 70′-80′ persisting it.

This is my summary:

  • Epics are redefined by SAFe in a hierarchy of epics and user stories that try to accommodate and institutionalise, as accepted normality, component teams that cannot create autonomously an end-to-end slice of functionality, and accommodates the top-down separation between those that plan the work and those that do the work. The definition of Epic as understood by Agile practitioners is substantially different, it encourages conversations among anyone involved in the work to do at every level, and it encourages cross-functional teams able to deliver autonomously a slice of a functionality, it also encourages frequent releases to keep in sync everyone involved with a piece of work to be done.
  • PI planning focus, just like in 70′ and 80′ practices, is mainly on identifying and scheduling the work and in accommodating existing dependencies. The Agile approach instead is to have teams and team members to pool the work and organise it and organise themselves to minimise dependencies while working on removing incidental dependencies and relaxing the remaining ones.
  • Agile Release Train accommodates the need for multiple teams to release together and encourages synchronisation, standardisation and conformity because expects all teams to adopt the same approach and the same development and release cycle that in turn increases the effort needed for coordination. It is well known that scaled systems rely heavily on asynchronicity. And the Agile approach is to encourage adaptations to each team own circumstances and to work toward enabling each team ability to release independently.

U.S. Air Force CSO Nicolas M. Chaillan, December 2019

Nicolas M. Chaillan is the Chief Software Officer at the U.S. Air Force and the Co-Lead for the DoD Enterprise DevSecOps Initiative.

During the event ‘DoD Enterprise DevSecOps Initiative Ask Me Anything’ Nicolas M. Chaillan comments on questions about his Memorandum for Record on Nov 26th 2019, sent to all PEOs and PMs regarding the use of DevSecOps and Agile.

The memorandum is “highly discouraging from using rigid, prescriptive frameworks such as the Scaled Agile Framework (SAFe).

Here follow a few excerpts from the comments about SAFe in this slide:

Slide 12 of the unclassified slide deck v1.0: DoD Enterprise DevSecOps Initiative Ask Me Anything Event
  • Bloated overhead functions (Waterfall-like)
  • SAFe isn’t used by any successful software commercial organization (Facebook, Google, Netflix, etc.)
  • Fundamentally, the main “goal” of Software development is NOT to be « SAFE », it is to INNOVATE and CREATE. You do not create by not taking risks… it is quite the opposite
  • until we can truly implement basic Scrum/Kanban, there is nothing to « SCALE »
  • You cannot scale if you don’t have the “basics” right.
  • « Continuous Learning: Fail Fast but don’t Fail twice for the same reason! »

The slides & as well as the video of the event are available here: https://software.af.mil/dsop/documents/

Since the publication of this report from USAF, Scaled Agile Inc offered to work for USAF to address the comments above.
Meanwhile, Nicolas M. Chaillan clarified: “my memo on SAFe still stands regarding my take on SAFe with DevSecOps. Until the issues mentioned in the memo are fully addressed with a released update of SAFe, SAFe is still not recommended to be used in conjunction with DevSecOps.” (link).

Mary Poppendieck, December 2019

Mary Poppendieck started her career as a process control programmer, moved on to manage the IT department of a manufacturing plant, and then ended up in product development, where she was both a product champion and department manager.

She is the co-author, with his husband Tom Poppendieck, of the award-winning book Lean Software Development: An Agile Toolkit. A seminal book for the Agile community that translates the lean manufacturing principles and practices to the software development domain. She is the author of several other successful books and she is a world renewed speaker.

About SAFe she comments here, referring to the slide above (Questions about Agile / SAFe, from the U.S. Air Force CSO Nicolas M. Chaillan):

<< I am often asked what I think about scaled agile frameworks. This slide does a good job of summing up my viewpoint, except for the last point. We need more research on how successful large companies coordinate the work of small autonomous teams to achieve larger goals. >>

The point she disagrees with is this:
– Looking to coordinate your Product Owners’ work? Multiple models exist such as Scrum of Scrums etc. This shouldn’t impact the developers.

Mike Beedle, January 2017

Mile Beedle was an American theoretical physicist turned software engineer. and he was the author of the first book and earliest papers about Scrum. He was also a co-author and a signatory of the Agile Manifesto.

He wrote that “S_Fe is not Agile”, and he added, “There are many other better choices”. He articulated how SAFe in particular and the Agile Train Releases concept, violate all the values in the Agile Manifesto. A copy of his original post is included in this post.

ThoughtWorks, April 2016

ThoughtWorks, a global technology company that’s unanimously considered an authority in Lean and Agile, explicitly discourage the use of SAFe, and suggests Lean alternatives because actual SAFe adoptions are prone to over-standardisation, resulting in practices that hinder Agile adoption:


ThoughtWorks update their comments and recommendations whenever they feel that something new has happened. So their comments and assessments can be considered actual even after the publishing date.

Alistair Cockburn, 2016

Alistair Cockburn is a methodologist, the creator of Crystal Clear and the Crystal family, and more recently he launched the Heart of Agile movement. He is also a co-author and one of the 17 original signatories of the Agile Manifesto.

During a meetup in London on June 2016 (video from minute 35) he suggested that the money and time spent on installing SAFe could produce much better results when spent instead on improving collaboration and delivery that in turn would move the company attitude and behaviour some distance. He added at that point that he stopped defending SAFe because he thinks there is a better spend of the money.

Martin Fowler, 2014

Martin Fowler is Chief Scientist in ThoughtWorks, so you can imagine that the view of ThoughtWorks on SAFe, also documented here, is congruent with his view. He is also a co-author and one of the 17 original signatories of the Agile Manifesto.

Colourfully, during a panel at the GOTO conference, he jokes saying “SAFe stands for the Shitty Agile For Enterprises, as my friend calls it.”

Dave Snowden, 2014

David John Snowden, a researcher in the field of knowledge management, creator of the Cynefin framework applied in software development and management science, says that SAFe employs ordered world approaches to solve complex problems, and because of that it’s a-priori wrong, wrong in principle.

As a result, SAFe is a backwards not a forwards move. Even more, he says that SAFe “is a massive retrograde step”

Read Dave’s article about SAFe: Is it SAFe?

Commenting to this article Dave adds:

“People keep railing against it because it is a backwards not a forwards move. The fact that it’s a pyramid selling scheme for accreditation and training is a commercial success does not validate it, any more than people voting for Donald Trump validates narrow-minded bigotry. The Agile community needs to face up to the need to improve delivery rather than make money from accreditation in large rollouts that are not (and will not) be sustained. Just like Sick Stigma and others, the big roll out is an excuse to do nothing real and just carry on as before.”

Ken Schwaber, 2013

Ken Schwaber, is a software developer and product manager. He worked with Jeff Sutherland to formulate the initial versions of the Scrum. He is also a co-author and one of the 17 original signatories of the Agile Manifesto.

In a blog post, he equates SAFe with RUP that is an old heavyweight methodology that is worlds apart from Agile.

Barry W. Boehm, 2012

Barry W. Boehm is a prominent American software engineer and author of the COCOMO costing model and the Spiral Model software process. He comments on the approach embraced by SAFe: “Tailoring-down all-inclusive methods lead to unnecessary expenses in time and resources”, and he adds that it’s the opposite of the Agile approach. (FYI I couldn’t find the original article reporting these quotes, my search concludes that the most probable source of the quotes is the book Balancing Agility and Discipline: A Guide for the Perplexed).