The traditional tools and techniques used for gathering requirements have not served us well. We usually get ahead of ourselves and start embedding design into our requirements specifications. We spend either too little or too much effort. We create prototypes that are helpful but are also distracting, and we create contract-style requirements lists that are difficult to use and don't provide any checks or balances . There must be a better way. |