The problem is Agile. Not the way it was intended at some point, but the way it has become through Agile consultants and SAFe. Also the fact that it's become the default for any project and that Waterfall has become a bad word.
Companies abuse Agile so they don't have to plan or think about stuff anymore. In the past decade, I haven't worked in (or seen) a single team that had had more than 2 weeks of work prepared and designed. This leads to something build 4 weeks ago needing a massive refactor, because we only just realized we would be building something conflicting.
That refactor never happens though, because it takes too much time, so we just find a way to slap the new feature on top of the old one. That then leads to a spaghetti mess and every small change introduces a ton of (un)expected issues.
Sometimes I wish we could just think about stuff for a couple of months with a team of designers before actually starting a multi-year project.
Of course, this way of working is great when you don't know what you'll be building, in an innovative start-up that might pivot 8 times before finding product-market fit. But that's not what many of us in big corp and gov are doing, yet we're using the same process.
This, 100%. Agile (properly done, for whatever value of “proper“ you choose) is fine for websites, apps, consumer facing stuff. For things that must work, in predictable fashion, for years, it’s often inappropriate.
OS work is somewhere in between, but definitely more towards the latter category.
Companies abuse Agile so they don't have to plan or think about stuff anymore. In the past decade, I haven't worked in (or seen) a single team that had had more than 2 weeks of work prepared and designed. This leads to something build 4 weeks ago needing a massive refactor, because we only just realized we would be building something conflicting.
That refactor never happens though, because it takes too much time, so we just find a way to slap the new feature on top of the old one. That then leads to a spaghetti mess and every small change introduces a ton of (un)expected issues.
Sometimes I wish we could just think about stuff for a couple of months with a team of designers before actually starting a multi-year project.
Of course, this way of working is great when you don't know what you'll be building, in an innovative start-up that might pivot 8 times before finding product-market fit. But that's not what many of us in big corp and gov are doing, yet we're using the same process.