Very nice article. I would also like to add that writing features definitely helps in providing a sound MVP. I'm quite surprised that nobody thinks that one of

Very nice article. I would also like to add that writing features definitely helps in providing a sound MVP. I'm quite surprised that nobody thinks that one of the reasons a MVP fails can be the quality of such MVP, where quality != number of features. Writing Gherkin features shows clearly what kind of application flow I'm implementing, and it happens a lot of time that I notice a step that is just unnecessary or overly complicated. Even mockups are not as meaningful as scenarios, because they don't describe the application flow or state changes. I'm not saying that you must use BDD, only that to me it's very useful to do so for my own startup, that's all. Reading the other posts it also seems that people spends a lot of time testing unnecessary things, like a facebook login. Guys, just shoot a mock object that returns true or false, Facebook works, trust me :) I agree with the article about all the other points.