First of all, I don't believe SAFe is actually agile at all. There are some good things with the framework, but as usual, Chevron screwed it up and allowed that growth mindset of not just IT, but also of our key CTC VPs to also scale uncontrollably. This is why we are doing fake agile instead of real agile:
1) No one is talking with or observing the software users and there is no continuous feedback loop between users and teams; there are no true end users. The "end users" are representatives from UC/ETC. Not from a BU team member who will actually use it: The product owners at Chevron are not the actual end users. Example: D2D project spends almost 100 million bucks on products run by supply chain when the end users are field operators. Remember last year when D2D was the sh!t? Does anybody speak about D2D anymore? That's because they weren't agile at all. Internal teams giving themselves kudos, and product owners who don't even really know the end users because the end users don't have time for them.
2) There is a strong emphasis on requirements: these people get a kick out of adding c-ap to the backlog and tracking dashboards in ADO. They assign fake value to every story. They make up their own features. But these requirements sure are well-written in ADO!!
3) Manual processes are tolerated: Example - the consultants staff up enormous teams including QA testers even though testing should be automated. You don't need them at all. Another example - everything that cannot be done inside ADO is actually all manual. Scrum masters and RTEs are not professionals at Chevron.
All the people who absolutely hate SAFe are those who have already been doing agile for years...
PROVE ME WRONG.