"projects with clear requirements documented before development started were 97 percent more likely to succeed."
I believe Barry boehm is on record stating that the biggest mistake he made in designing a software creation process was believing people who told him that you could get firm requirements up front.
So yes, if you're in that rare case where you can start out with clear and non-contradictory requirements, probably anything you do is going to succeed better than when you don't.
There's a good book on risk management that goes into this more, Waltzing With Bears, by Demarco and Lister
I believe Barry boehm is on record stating that the biggest mistake he made in designing a software creation process was believing people who told him that you could get firm requirements up front.
So yes, if you're in that rare case where you can start out with clear and non-contradictory requirements, probably anything you do is going to succeed better than when you don't.
There's a good book on risk management that goes into this more, Waltzing With Bears, by Demarco and Lister