Yea, Agile in semi/HW industry is pure cancer. Innovations in this industry come as you let your engineers take their time to try out a million things that don't work in order to eventually, after months or even years, get to that one thing that does work, not by shoving them in the Agile meat grinder of daily standups, sprints, TPS reports, velocity charts, grooming meetings, etc.
Agile in HW only "works" when your company is a sweatshop, operating on low margins, bind by churning out commodity stuff in volume to demanding customers (i.e. Apple) on a strict cadence with the fear that if you don't deliver on time and under budget, then they go somewhere else, so you hire some Agile consultants to act as whip-crakcers and henchmen of management to make sure your devs are busy bees and ship, ship, ship.
I assume this is not the case with ASML (and maybe also with the likes of Nvidia, etc.) as they're the tip of the spear and so far ahead of the competition that they can take their time and charge however much they want and their customers have no other choice but to wait and pay up as there's nobody else to go to for competitive alternatives in the bleeding edge space.
agile with lowercase ‘a’ was defined for software development (https://agilemanifesto.org/), so you cannot blame it for not applying fully to hardware development.
The manifesto is extremely flexible, though (it doesn’t mention standup or fixed-length sprints, for example), so I think it can work for hardware, too, but you likely have to make the sprints longer and be more flexible in lengthening or shortening them to match reality, maybe do more documentation, etc.
I think ”half year sprints” loosely is how the Apollo program was run (https://en.wikipedia.org/wiki/List_of_Apollo_missions), certainly after Apollo 1, when they realized the schedule wasn’t the most important thing in the world.
https://en.wikipedia.org/wiki/Apollo_1#Program_recovery: “We were too 'gung-ho' about the schedule and we blocked out all of the problems we saw each day in our work. Every element of the program was in trouble and so were we.”
The dogma of Agile with a capital “A”, on the other hand, IMO, doesn’t work for anything, be it software or hardware.
