3 ms·
Someone at my last job threatened to quit if they implemented SAFe. My current employer has implemented it and now I'm actively looking for another job.
by jzackpete 5y ago
Someone at my last job threatened to quit if they implemented SAFe. My current employer has implemented it and now I'm actively looking for another job.
- brightball 5y agoI probably need to do a blog post on this exact subject. As a dev of 20+ years, I got into SAFe because it's IMHO the ideal work environment for developers. It's supposed to put developers in control of the schedule, prevent you from being handed arbitrary deadlines, avoid constant changes in priority by letting teams plan out for a quarter at a time, avoid over planning the time you have (2/3 of time planned per 2 week iteration and 2 full weeks at the end left entirely open) and make sure everybody is clear up front about what the risks are to being able to deliver on the plan. There's supposed to be 2 backlogs, one for the product side to prioritize and one for the dev side to prioritize without any influence from product so that you can ensure all of the technical stuff that needs to be done can be done without having to spend a ton of time explaining why to the non-technical side of the house. End of the day you should end up with less meetings and a more realistic schedule that you, the developer, have essentially created. If leadership won't give up the control to let the process work, everything goes to crap. Every place I've heard of bad SAFe experiences, that's been the cause fwiw. Usually the most frustrated people in a SAFe are the micromanagers (and it's supposed to be that way). Would you be willing to share why it's going so wrong? My keybase contact info is in my profile.