The additional “e” making SAFe “safe” is an excellent marketing consideration. SAF + “e” is safe to do. SAFe adds a level of safety by lowering risk.
What is it?
It is a guide of things to do for large development teams to work in an agile way.
When I see guide, I mean it. It has descriptions on what meetings/ceremonies you should have, what each persons role responsibilities are, and how each member should be able to connect with one another.
When would you want it?
Because managing 50 developers can be difficult, especially if they don’t work as one team.
Large corperations/organisations have a lot of developers working on a lot of related and dependent things. Working in a typical waterfall* way can cause large problems — specifically in addressing what customers want and having to retroactively change. At it’s core agile* methodologies are made to address this and allow development teams to iterate and ship products early. The problem is that Agile ways of working were built and defined for small teams (daily stand-ups, pivoting if an when necessary, anyone should be able to influence anything).
This can be a tricky thing to manage as more and more people get involved. You could silo people into…
