4 ms·
I don't really understand SAFe, but from the outside looking in, it seems like the answer to "How close can we get to agile while still employing an army of Pro
by ineptech 4y ago
I don't really understand SAFe, but from the outside looking in, it seems like the answer to "How close can we get to agile while still employing an army of Project Managers?" Which is to say, not very.
- vesinisa 4y agoSAFe not only keeps middle managers employed and feeling important but also forces lots of unnecessary pencil pusher type work on the engineers and designers. It's a strain on all parts of the organization that are forced to use it. This is why most companies will abandon SAFe after a couple of years, like the case studies show. I have personally left one employer (a bank) because SAFe made the job unbearable. Both this company and their larger competitor abandoned SAFe after a couple of years. I now categorically ignore any gigs and openings at companies using SAFe - it's a glowing red flag to me.
- teeray 4y agoI have also left an employer with MBAs that continually tried to find and mandate the One True Way of building software. I noped out when I found myself in multiple status meetings every day repeating myself to different middle managers (and having to update a Slack status channel as well). Spoiler: they adopted SAFe after I left, which told me everything I needed to know about SAFe without having to experience it firsthand.