In every business process, it is important to perform requirements analysis at the beginning of any development method. Requirements analysis is the process of obtaining information from the client, investigating this information, subdividing them into atomic particles that are easy to undertake, and transforming them into a feasible plan. Without performing requirements analysis, the chance of failing the development process is huge. The process of agile requirements gathering is the primary step in requirements analysis. Through face-to-face customer meeting, e-mail exchanges, telephone conversations, and surveys, the developer can acquire the necessary information he needs to set out a guideline for actual development. It is best that the all information acquired from the client are recorded and stored for future references.
When the information is already available, business analysis requirements is performed. During this process, the requests of the client are translated into qualitative and quantitative specifications which are easily understood by the development team. These specifications will serve as the main reference during actual project development.
Once the raw information has been translated to functional specifications, the final plan is created. This plan is reviewed to determine whether there are possible flaws and loopholes that may occur during development. It is known that it will be better to find a problem before the actual processes are done than during the performance of the processes. When approved, the plan is sent to the development team to start the creation of the product. Every now and then, the team checks with the plan to see if they are still on track or adjustments should be made.