About Requirements Management
Requirements Management is the process of eliciting, documenting, analyzing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project.
UWM uses a methodology for requirements management that was developed by the International Institute of Business Analysis (IIBA). The requirements management initiative at UWM is coordinated through the Process Management Office in University Information Technology Services (UITS). For more information on services offered by Process Management, or inquiries regarding requirements management, please contact firstname.lastname@example.org
The requirements management process has the following five steps:
- Elicitation - The Business Requirements Analyst works with all stakeholders in a project to list all of the requirements for the system. This is usually done according to role, with stakeholders contributing requirements for the role they represent.
- Analysis - Once the basic requirements have been identified, the requirements must be made to conform with a number of characteristics.
- Representation/Documentation - this phase in the requirements management process puts the requirements in a form that can be reviewed by others.
- Validation - The validation phase is where stakeholder state their acceptance of the requirements. This is done through a consensus exercise where each requirement is individually validated by a representative group of stakeholders. Rather than having stakeholders responsible for signing off on a full document, a facilitated exercise is conducted where each stakeholder reviews each individual item in turn.
- Change Management - Once all of the above steps have been completed, and an approved set of requirements exist, there needs to be a mechanism to change the requirements if such change is necessary
Below you can see an overview diagram of the process. Please note that for simplicity, some of the iterative steps have been left out. Please also note that the change management process has been omitted from this diagram. Since communication with stakeholders and sponsors should be happening in all phases of the process, a communication component has been added to the diagram.