I doubt that there is any one answer to a question like this. What field are you talking about? If it is a performance critical application like code for hospi

I doubt that there is any one answer to a question like this. What field are you talking about? If it is a performance critical application like code for hospitals or intelligent life support systems/medical devices then certainly one would go for B. On the other hand if you're designing a UI then there is no one way to do it. It's true that Apple releases only one update in a long time but they make hundreds of prototypes and test them out like anything (see: http://developer.apple.com/mac/library/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGIntro/XHIGIntro.html http://developer.apple.com/mac/library/documentation/UserExp...). So they do a clever combination of A+B, while maintaining their image. However, if you're small then you can't afford to hire professional testers to test everything, or do videotaped randomized trials with volunteers who have signed a NDA. So, then a release often and correct often strategy would work well for you. The question should be; How should I decide which one is better for me? A, B or A+B in some permutation? [note: I am assuming that B in its pure form means micro-managed code that is proactively developed to be perfect from the start based on some previous parameters.]