At my current workplace, we do have a roadmap for the business, but the actual backlog of tickets to implement work is all waiting on other siloed teams to make decisions that we are downstream of. This ranges from our infrastructure model to simple things like “which CSS components are we allowed to use.”
We are also explicitly NOT allowed to make any code changes that aren’t part of a story that our product owner has approved and prioritized.
The result is that we scrape together some stories to work on every sprint, but if we finish it early, we quickly run into red tape and circular conversations with other “decision makers” who need to tell us what we’re allowed to do before we actually do anything.
It’s fairly maddening. The whole org is hamstrung by a few workaholic individuals who control decision making for several teams and are chronically unavailable as a result.
I’ve seen this sort of thing happen at other big enterprises too but my current situation is perhaps an extreme example of dysfunction. Point being, when an org gets tangled up like this, LLMs aren’t gonna save it :)
The moment those people start being removed, and the little work they do automated, it’ll have a dramatic downstream effect.
I’ve already witnessed a certain big tech that started to move much faster by removing TPMs & EMs across the board, even without LLMs to “replace” them. With LLMs, you need even fewer layers. Then eventually fewer middle-of-business decision makers. In your example, it’s entirely possible that the function of making those components could be entirely subsumed by a single AI bot. That’s starting to happen a lot in the devops space already.
All that said, I doubt your business would benefit from moving faster anyway - most businesses don’t actually need to move faster. I highly recommend the “Bullshit Jobs” book, on this matter. Businesses will just need fewer and fewer people
We are also explicitly NOT allowed to make any code changes that aren’t part of a story that our product owner has approved and prioritized.
The result is that we scrape together some stories to work on every sprint, but if we finish it early, we quickly run into red tape and circular conversations with other “decision makers” who need to tell us what we’re allowed to do before we actually do anything.
It’s fairly maddening. The whole org is hamstrung by a few workaholic individuals who control decision making for several teams and are chronically unavailable as a result.
I’ve seen this sort of thing happen at other big enterprises too but my current situation is perhaps an extreme example of dysfunction. Point being, when an org gets tangled up like this, LLMs aren’t gonna save it :)