The thing that disrupted waterfall was not Agile per se. It was the fact that no one could figure out why waterfall was appropriate in some contexts but not in others. This led to pervasive conflict between stakeholders who wanted correct answers and those who wanted immediate answers. The remedy, obviously, was: shiny process! -- including, but not limited to, Agile. Today, new shiny processes; but the question is still whether the answers should be right or fast. Pick one.
I don't think Agile is dying, but it needs to evolve with the times. Much of the heavy process with Agile (and SAFe) that got created was due to managing large teams of humans. With AI in the mix, things change - but the core elements of shipping frequent value and getting feedback to improve the product is still critical
Could be the case! Without being to strict on the terminology I just wanted to give a clear message: Our planning processes and time range expectations are changing completely
Staying pretty much the same, at least with the current state of technology (just way more bottlenecked by this, but with the same process). What have you seen?