Requirement Management Guide
- 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
1. Stakeholder roles and responsibilities:
The requirements definition process begins with the elicitation of stakeholder requirements, the first step of which is to identify the stakeholders from whom those requirements are to be gathered.
This section outlines the roles the stakeholders have, along with the responsibilities they will undertake in the process of requirements management.
Who is a stakeholder?
A stakeholder is anyone who has a stake in the project, someone who is affected by the system in some way or can affect the system in some way. The following can be the typical set of responsibilities and roles, in case of a generic, conventional project.
a) Creation of the RMP (Requirements Management Plan)
Business analysts or project managers, or business analysts with inputs from managers are responsible for the creation of the RMP.
b) Approval of the RMP
The stakeholders that are in leadership roles, in charge of decision making; be it the project management team, the product development team, product owners and clients, leaders from each of the phases of the product’s development, or other uniquely defined external stakeholders are in charge of approving an RMP.
1. 1. Participants and their responsibilities in the requirements management process:
a) Project managers:
Monitoring and tracking the entire progression of a requirement throughout the lifecycle of the project, reporting project status, and metrics based on the root requirements.
b) Business analysts:
Gathering, analyzing, and documenting requirements and updating the requirements management plan as and when required.
c) Subject matter experts:
Interpreting and analyzing stakeholders’ needs and converting them into actionable requirements.
d) Design solution architects:
Progressing requirements towards functionalities by designing solutions
Developing designed solutions into tangible functionality
Verifying whether the designed and developed solution satisfies the requirement
g) Change management analysts:
Determining organizational change due to requirements, communicating, and managing change.