Ask HN: Better tools for the software requirements / scoping phase?
The underlying assumption with requirements is often not stated explicitly: that people _can know_ everything in detail, in advance.<p>If that is the case, surely we can find better ways to uncover the requirements, and better tooling will help solve the problem.<p>Experience tells me that people don’t know everything beforehand. Thus the key assumption is not valid.<p>Then the question we should be asking is: how do we most efficiently bring people to where they discover and understand the requirements?<p>Experience tells me people are much better at giving concrete, specific feedback to a running system than to an abstract requirements document.<p>Hence iterative development.<p>In essence requirements are not a document by a process.