Requirement Management Guide
What is requirements management?
Why is requirements management important?
How are requirements managed in an organization?
- Stakeholder roles and responsibilities
- Requirements gathering & management process
- Types of requirements
- Requirements artifacts
- Requirements naming and versioning convention
- Requirements prioritization
- Requirements traceability
- Requirements versioning
- Requirements baseline
Requirements Change Management
2. Requirements gathering and management process
The requirements management process typically contains five major parts that further contain sub-processes. These parts can be categorized as the requirement gathering phase, the refining and categorizing phase, requirements communication & negotiation, and the sign-off and monitor.
2.1 Requirements gathering:
In this phase, the project team identifies the stakeholders and communicates with them, elicits their needs, and identifies opportunities and problems by using various requirement gathering techniques such as:
- Document Analysis
- Focus Group
- Interface Analysis
- Questionnaires / Surveys
- Requirement Workshops / JAD Sessions
- Research and Observations
2.2 Refining and Categorizing :
2.2.1 Analyzing requirements:
The stakeholders’ needs are refined, interpreted, and converted into requirements.
The analysis can consist of the following stages:
- Sufficiently word and detail the requirements
- Identify which requirements are the most critical, and which are “nice-to-haves”.
- Carry out an impact analysis for each need
- Analyze feasibility
2.2.2 Specifying, documenting requirements:
The requirements are authored and documented in a formal, conventional language that will be understood by the team that will be working on them. Most teams typically prepare a written document, sometimes called the RSD of the Requirements Specification Document, to formalize and detail the analysis to be presented to stakeholders and clients and the product development team. These days, requirement authoring, documentation, and management software make it really simple to prepare detailed and accurate requirement artifacts.
2.3 Communication and negotiation:
Baseline requirement groups: In this phase, the requirements extracted from the stakeholders, interpreted, and documented, are communicated to the stakeholders to be verified, validated, and prioritized. This phase involves negotiation and coming up with groups of requirements prioritized, categorized, verified, and approved.
The negotiation process can typically go as follows:
- Studying stakeholders and their needs
- Thoroughly knowing your proposed system and the problems of the existing system that you are solving
- Asking open questions
- Listening and understanding
- Setting some ground rules
- Deploying a suitable negotiation method, depending on the stakeholders.
e.g., The P2O2 method;
People: Separate the persons from the problems
Positions: Focus on the interest, not the position
Options: Generate favorable and unfavorable options (but with adequate mutual gain)
Objective criteria: Make decisions based on objective criteria
- Justify your position
- Know your bottom line
- Be prepared for favorable, as well as unfavorable outcomes.
2.4 Signing off and monitoring
This phase involves two stages, signing off on the outcomes of the requirement communication and negotiation stage, and monitoring those requirements, monitoring changes and managing them, and ensuring that all involved parties are on the same page in terms of what has been agreed to and how it is progressing.
Sign offs are a legitimate indication that the deliverables have been formally agreed upon and that the stakeholders understand the requirements specification document.