How do I know which requirements should be retained for reuse?

It isn't easy to guess which of your requirements will be useful for future projects. Some people may want to retain them, while others won't care. The team supporting the solution after implementation will benefit from holding onto the requirements package and the technical design, as an aid for managing issues and changes along the way. But the business may not show much interest in retaining the requirements for future use. Still, it's good for everyone to be aware of the ways in which requirements documents can have value beyond the immediate project. Here are some tips for deciding what to keep.…

Log in or Subscribe now to read the full answer...