Martin, in your article you make good points about how requirements documents have been misused in the past. I agree that having a great team that is communicating and collaborating frequently is ultimately more important than any document, and that the product should evolve over time in an iterative process. However, I feel there is a middle ground where we can pair down the initial documentation step to be a good starting point for the first few sprints. Without a definition of we think the software is going to be, it is impossible to estimate the time and money it will take to build it, which is very important for many entrepreneurs to know.