37signals' Jason Fried describes a good idea for requirements documents:
Like most specs, this spec details the key features and wish list for the web-based application. However, after each feature description they boil it down and say “at the very least” it needs to do this. So, in other words, we’d love it if it would do A B C and D, but at the very least it needs to do A.
Posted by Karl
May 15, 2004 10:15 AM