Requirement Management is the process of systematically organizing, documenting, prioritizing the requirements of a project. It is an on-going process that continues through-out the life-cycle.
The stakeholder identification process is one of the most important processes in a project because projects are undertaken to fulfill the requirements of the stakeholders. Key stakeholder should be identified in the beginning of the project and ensure that they are involved and engaged throughout the project span. Projects are successful, if stakeholders are happy.
Elicitations techniques for requirement gathering
A requirements can be gathered by using the below elicitation techniques
- Documents Analysis
- Reverse Engineering
- Focus Group
- Joint Application Developments
Sort the requirements
After adopting the above elicitation techniques, requirements are sorted with their relevance and interlinked. At this stage, stakeholder’s needs are defined; requirements are divided into functional and non-functional requirements, group of requirements with similar nature are brought together, and supporting artifacts are created.
In this stage, requirements are lined –up for the development process. Many techniques can be used for prioritizing. Naming some are 100 $ test, top 10 requirements, Numerical, Assignments and MoSCoW.
This technique is used to prioritize the requirements in to Must have, Should have, Could have and Would like to have. Particularly it is more useful when agile software development approaches, where there is more to do than there is a time or funding to permit.
Requirements should be validate from time –to-time, to ensure that stakeholders, solution and transition requirements are aligned with the business requirements. There are certain techniques to validate the requirements such as FURPS, CUCV, CAE, APVU and SMART. Among all SMART is the most popular or relevant technique.
S – Specific
A – Attainable
R – Relevant
T -Traceable/Time bound