Documenting and Managing Requirements
This is a detailed how-to guide to ensuring your requirements are fully captured. It is a useful guidebook with processes you will tweak and adapt to each project plan. Is anything surprising or new to you? You will not use all of these approaches for every project, but having them at hand is useful when planning your next project.
Requirements Management
Appropriate to the Recipient
Communications should always be presented at a level that is appropriate to the recipient of the information. The level of communication required for individual stakeholders should be matched to the role the person plays in the execution of the project.
For example, the Executives may receive an Executive Summary Requirements Document that presents the requirements at a very high level. SMEs and other stakeholders may review the mid-level functional requirements that describe what inputs, outputs, behavior, and capabilities are needed. Detailed functional and system requirements are needed by the development and quality assurance staff.
Using these various levels when communicating about requirements will prevent recipients from receiving too much information, or not enough, for their purposes.