113 ms·
Ugh, SAFe. My group has been trying to implement this methodology for well over a year. My observations: * Program increment planning is absolutely painful.
by bmj 4y ago
Ugh, SAFe. My group has been trying to implement this methodology for well over a year. My observations:
* Program increment planning is absolutely painful. Three full days of meetings, and rarely do the stakeholders come with fully refined features. And, typically, what plan emerges is changed within two weeks because of emergencies or an executive seeing a shiny bauble we absolutely need to have.
* Two week sprints seem too short, at least for a group working in a highly regulated industry that requires a ton of manual testing and paperwork. I will also admit that we likely have trouble writing appropriately sized stories, but part of that circles back to the need for massive validation efforts.
* We suffer from lots of turnover in product management (and perhaps too many product managers). If a PM leaves, their features tend to die on the vine, even if some executive has decided they are important. That leaves us with a massive backlog.
- ethbr0 4y ago> highly regulated industry that requires a ton of manual testing and paperwork This describes every industry for a company I've seen SAFe at. Or, in other words, SAFe is: {how do we say we're doing Agile?} + {how do we avoid changing any of our regulatory compliance pipelines?} = {business as usual} + {a bunch of extra useless Agile theater}
- iamthepieman 4y agoYou're not working for a big company in Atlanta are you?
- bmj 4y agoNo.