Purpose of requirements management in projects; The management of all technical or non-technical requirements required by the project, and the determination of the incompatibilities between the project plan and the work that is being prepared.
Managing this analysis with requirements analysis directly impacts the success of all processes in the software development lifecycle within a project cycle. For this reason, it is important that the “needs analysis” is carried out in accordance with the right and the targets.
You can learn more about project management through a PMP online prep course
The requirements process, which is included in the requirements analysis, consists of 4 main headings;
1.Building (Feasibility) Study:
It is the process of determining whether customer needs are within the appropriate budget and technology boundaries. It should be indicated to the clients that there is an additional cost of the extra services required and that this should be both time and materially sufficient. Sometimes the available technology may be inadequate. It is therefore necessary to carry out the charity work for all requirements.
A feasibility report should be prepared as a result of the feasibility study. Possibility studies can be made in different forms: technical feasibility (resource, technology, etc.), economic feasibility, legality, etc.
In the case study, it is also useful to make profitability-cost analysis and decide according to certain criteria. Costs must be set for each service and vehicle, and decisions must be made in the light of expectations, risks and priority values.
- Requirement Analysis:
It is to reveal the expectations of the client and the project from all the stakeholders in the system and to separate them with appropriate methodologies. Especially it is very important that conflict management is done in this process and if there are inconsistencies. Prioritization of requirements is also included in this process. From the client’s point of view, all requirements are the same priority or not visible. If there is a project plan and budget, some requirements will need to have a higher priority.
Requirement definition: It is necessary to make the necessary definitions by transforming the requirements into the forms that the customer can understand. Diagrams or forms are used in this process and a structured document is prepared visually. It is a step towards the customer.
Detailed requirement specification: It is the process of defining requirements and revealing common and non-common points. Software design is introduced. This process is mostly for those who develop the application and technical stakeholders in the customer environment. Detailed forms and diagrams are created for each of the forms resulting from the requirement definition process. Abstract definitions are defined for the objects that will be defined in the design of the software, and the data flow diagram is created at the top level.
Another way to develop requirements is to build and prototype the deficiencies of previous requirements by presenting the prototype to the client.
You can check PMP sample exam questions.
3.Confirmation and Verification:
All need documents (use-case documents, etc.) must be officially approved by the client. Taking requirements without designation as customer input can lead to a faulty project cycle, and most importantly, waste of effort. It is important that this approval and verification process be carried out in order to more easily identify the cost of the potential requirement changes and the revision of the project plan.
It is the use of checklists to verify requirements. It is imperative to ensure that all the criteria in the checklist are met and to complete the deficiencies.
Requirements management; Business, organizational change, as well as the control and management of technical changes. It is in this activity that the organization of customer meetings and meetings and documentation of the requirements obtained are analyzed.
Learn more at Master of Project Academy Blog