Here is my prediction:
The Magnificent Seven - Alphabet, Amazon, Apple, Meta, Microsoft, Nvidia, and Tesla - will continue to push AI down our throats despite diminishing returns to its users, simply because they’ve invested so much they’ve gone past a point of no return.
That notwithstanding, the inevitable Great Implosion will happen to companies such as Anthropic and OpenAI because open source models that can be run locally - with minimal capex and zero risk of surveillance - are quickly and irreversibly becoming good enough.
The whole ”AGI is just around the corner” is a meaningless and silly distraction.
I'm not a fan of Scrum Retrospective meetings. My two main issues are that they don't happen often enough, and they often follow some ridiculous formula.
Addressing the first issue, I'd rather follow Kaizen principles. Improve every minute of every hour of every day. When an improvement occurs to you, bring it to the team's attention and try it. When something goes wrong, pull the Andon Cord and stop working until the team can figure out how to ensure that the problem won't come up again. No formal recurring meetings are required, though by all means, have a meeting to solve problems that span teams or in other situations that might seem useful.
We used to have infrequent (e.g., quarterly) company-wide "retreats" where the entire department met offsite and worked on general improvements not related to any single problem. Those on a smaller scale are not a bad idea, either. Back when we all worked on big projects, a post-partum retreat (often called a post-mortem for some reason—the product had just been born, though, not died) was commonplace.
As for the formula thing, I think of these discussions as just that, discussions. Formulas seem to me to usually indicate some "coach" or manager throwing their weight around. If things are so chaotic that the team can't just have an informal conversation about improvement, make that the subject for your next retro, or better yet, deal with it right now.