[sidlls]

If I'm ever again in a SAFe team, something has gone terribly wrong. I won't join a company that uses this practice unless I'm very desperate. If a company I'm at adopts it after I've joined I will immediately begin looking elsewhere.

[brightball]

Yea, I'm very curious to hear more about this.

I've loved it at my company. It seems like development best practices + sanity enforcement outside of it and it's fairly flexible too (we use kanban instead of scrum).

It's done wonders for putting the planning of how things should be implemented into the hands of developers themselves and then essentially gets out of the way.

[C1sc0cat]

Why? reading Wikipedia this seems to be what used to be called RAD - done right its Fucking awesome.

One thing is you need 100% collocated experienced people who know what they are doing - no third party agencies who spend 15 mins discussing pixel separation in photoshop mock-ups.

It also not something you'd carelessly throw a junior or an intern into

[sidlls]

SAFe as I’ve seen and experienced it is a cumbersome, process-heavy system. Like most other project management systems currently in use in this industry it’s probably okay if 95% or more of the features are well-known and specified clearly. For any non-trivial software development work it’s a burden. For development touching other disciplines (e.g. statistics/ML, new product development) it’s more like an obstacle.

[brightball]

It is process heavy outside of the dev flow, but that is more business side so it shouldn’t affect devs themselves much.

It’s supposed to be getting out of the way of developers.