Do requirements have any residual value?

Do requirements developed for a project have any residual value, and if so what should I do with them?
Squiggles on cocktail napkins are a great way to make a point, or even talk through a solution. But they're hardly reusable, and they aren't a respected communications medium. If you want to avoid reinventing the wheel every time a project threatens to impact a system or business area, there's no substitute for clear, thorough, reusable requirements documentation. And the requirements documents are reusable when the organization takes on similar projects. In fact, that's a good argument for making the requirements documents as clean, organized, and easily retrievable as possible.

Retaining your requirements documents—for example, your software requirements specifications and product requirements specifications—helps guarantee consistent, efficient development processes and design standards for your applications and products.

©Copyright 2000-2018 Emprend, Inc. All Rights Reserved.
About us   Site Map   View current sponsorship opportunities (PDF)
Contact us for more information or e-mail
Terms of Service and Privacy Policy

Get Our Newsletter
Get our latest content delivered to your inbox, every other week. New case studies, articles, templates, online courses, and more. Check out our Newsletter Archive for past issues.

Follow Us!
Linked In Facebook Twitter RSS Feeds

Got a Question?
Drop us an email or call us toll free:
Learn more about ProjectConnections, our contributors, and our membership levels and product options.