CorrectĮach requirement must accurately describe the functionality to be built. Keep requirements details verbal instead of written also makes it hard for business analysts, developers, and testers to share a common understanding of the requirements set. Using minimal requirements specifications runs the risk of having different people fill in the blanks in different ways, based on different assumptions and decisions. However, projects using iterative or incremental development life cycles should have a complete set of requirements for each iteration. In most cases, you’ll never achieve that goal. Nothing says you need to make the entire requirements set complete before construction begins. Resolve all TBDs in each portion of the requirements before you proceed with construction of that portion. If you know you’re lacking certain information, use TBD (to be determined) as a standard flag to highlight these gaps. It must contain all the information necessary for the developer to design and implement that bit of functionality. Each requirement must fully describe the functionality to be delivered.
0 kommentar(er)
