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.
Introduction
Organizations spend a lot of money on key projects to ensure continued viability in a rapidly changing world. They invest in projects to solve a business problem, take advantage of an opportunity or implement a strategic solution that furthers business
goals. Capturing and managing the right requirements ensures avoidance of costly missteps and is key to delivering successful projects with measureable value.
In this Section of the Guidebook, readers should gain an understanding of the
activities that are associated with the documentation and management of project and application requirements. These activities support an organized methodology for performing Business Analysis throughout a project life cycle and enable an analyst
to position an organization to manage application projects and downstream maintenance in support of organizational strategies and work processes efficiently and effectively. Whether an analyst is involved in a project or initiative from the ground
level or 'Initiation' through enhancement changes or only involved in a part of the development life cycle, information contained in this section should provide guidance for the activities involved in the requirements management process.
Requirements Development
Requirements development includes activities related to gathering and analyzing the requirements.
Source: Wikibooks, https://en.wikibooks.org/wiki/Business_Analysis_Guidebook/Documenting_and_Managing_Requirements
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 License.