I have long returned back to waterfall, it just happens to take two weeks at a time.

Pure agile never worked on non-software industries, due to the way all parties expect to deal with requirements, demos, documentation, long term roadmaps, budget allocation for next year projects,...

Totally agree that non-software benefits from traditional project planning. In a project management class it was taught that the project framework should be adapted to the project.

It sounds really formal but planning how you plan the project is key for some things. For example, I would guess building a nuclear power plant isn't an iterative type of project. Lots of risks and lots of sequential activities. A team could probably spend weeks to months just planning the plan.

Even more basic examples, like when is the software ready with 100% feature capabilities, so that everyone can take a training.

Schedule, travel accommodations, teaching materials, trainers,.... need to be accounted for and planned on due time, on synch with go live for the new infrastructure.

"Small Consulting company promotes themselves by attacking Large Consulting company by playing off allegiances to tech religions"

https://devbizops.medium.com/are-you-tech-religious-fb281b39...