There is no reason to avoid iterations. And it is quite obvious that in a highly specialized field you want quick iterations to keep all the expensive specialis

There is no reason to avoid iterations. And it is quite obvious that in a highly specialized field you want quick iterations to keep all the expensive specialists occupied (in the OPs example, what do the developers do while the analysts analyse?). _BUT_ you cannot develop software without following the steps of the waterfall model. You need analysis. You need testing. And development has to happen in between. And here comes the problem: When you have a very fast iterative process, you have everyone working at high pace. But your quality will invariably suffer. If your analyst needs to come up with a decent distributed numerical solver for differential algebraic equations, they won't be done after two weeks. So their 'increment' is going to be incomplete. And no, Pareto does not apply to software specifications. The same holds for any other complex domain. And if your testers only have time to test for two weeks, they cannot cover as much as in half a year. So yes, iteration is a necessity and quick iteration has its merits. But it also comes with a cost and choosing the right pace is as difficult as it is important.