[dakiol]

I’ve worked for companies whose processes resemble what you described. It wasn’t bad at all. Things were delayed, sure, but it wasn’t a big deal (I never worked extra hours). I actually enjoyed it because it was pure joy to implement features with unclear requirements because that gave the engineers maximum flexibility (if something wasn’t implemented as needed, we would just say “alright, we’ll work on those new requirements, no problem, another sprint will be needed, though”

On the other hand I have worked for companies with a strict software development process. I’m not talking about waterfall, but agile: the systems were so over engineered that it was very difficult to write code (and it was an awful experience). Everything was done by seniors who left the company some time ago. You couldn’t really complain if you needed more time to implement something because our PMs were very clear about the requirements (so, if delays exist that’s not on them), and the code was written following good practices and standards (so again, if delays exist, is not because of the state of the code base).

I prefer to work for chaotic companies for a couple of years: more flexibility (so I can actually enjoy writing code) than for companies with obsessive practices.