It's more nuanced than pass/fail. ADDIE is useful if it's your FIRST port of call. And useless if it's your last.

The difficulty of writing requirements is only now becoming clear. And by 'clear', I mean that there are a generation of people who have actually experienced this. Complexity is no longer an abstract concept for anybody.

The advantages of speed are also becoming clear. Once, it seemed sensible to design then develop then implement. Ready, aim, fire. I'm not sure this is the case for the majority of activities now - DDI are often more effective when concurrent.

Sure, you can argue that ADDIE was 'meant' to be iterative, rapid and all the adjectives that the anti-ADDIE people would like their models to be. But this seems like the Sun Priest who argues that the harvest didn't come because the wrong type of knife was used during the sacrifice.

It's a useful mnemonic. Great for novices. A foundation for communication among professionals. But let's move on to something more interesting.