The role of BA includes a lot of multitasking and steps.
1-Requiremennt Collection- The BA here plays an important role by conducting several meetings with the client to understand their requirements via several interviewing techniques and other.
2-documentation- After the requirements are understood and is clear they need to be documented properly in a format and that needs to be confirmed after the documentation is dpone.
3-Analysis- The documented requirement needs to be analysed for its feasibility (considering the budget, time, resources) and then only the BA can proceed
4-Prioritisation- After the feasibility tests are done, requirements are placed according to their priority and are documented in the list, using MOSCOW.
5-Presentation- After the MOSCOW is applied, then there must be discussions with the other resources, on which the work needs to be done and then the work starts.
6-Bridging the GAP- The BA acts as a bridge between the client and the development team, who needs to act as mediator.
7-SDLC- The BA acts as mediator in the whole process, starting from the RG to the implementation of the software, so BA needs to be well aware of every stage of the project and if the development or the final product getting developed is according to the requirements or not.
8-End User Testing- It is the pilot project that a BA holds for the client to show him the development
9-UAT- The BA needs to convince the client about the final product developed and he needs to take sign off for the same from the client.
After the RG and RA is done, the approach strategy that is to be followed includes several steps such as the Business process modelling and where we need to identify the goals, the resources, the inputs and the outputs, the activities that needs to be followed for the process undertaken. After that BA needs to find out the strength and weakness using the SWOT analysis. After the threats and opportunities are find out the project feasibility needs to be done and must be find out if the time and budget provided is sufficient, Meanwhile the client has to provide the statement of work where BA got the confirmation about the project proceeds. After the feasibility analysis is done the GAP in the requirements or technology or infra needs to be found out so as to avoid any confusion and get the time for arrangement of the resources if lacking. Risk analysis also needs to be done to avoid any unexpected hindrances and provisions need to be made to avoid the same, such as technological or financial. And for avoiding any type of risk form the clients side the contractual work need to done prior to starting of the project. After all the analysis and confirmation is done BA needs to identify the interested parties and their onboarding needs to be done so that in case of any information sharing all the parties are informed simultaneously, and required informed decision is taken. After, this the BA needs to prepare the business case document where all the requirement and their purpose, needs, resources, expectation to be documented. Now the idea on how to proceed for the business is established and now the process through which the expected result is obtained is to be laid down. One of many established processes is followed depending upon the expected delivery time of the requirement. After every phase of the process is completed, the client should get the current status and the timesheet is to be forwarded every week or month so that the client can also check the proceeds and simultaneously release the fund for further tasks. After, the expected result is derived by the development and the testing time, which is also to be followed by BA every morning in 15 min meetings and the same is communicated on email. The same is forwarded to the client for UAT and if the client find it as expected then the client needs to sign off by signing on every document whose one copy needs to be archived and the other to be taken on email so as to communicate to every team member about the same. And if after UAT the client finds it not as expected he will not be giving the sign off and the onus lies in the team and the BA to again follow the whole process from the start. If there is some change request then in V model the change can be incorporated in between the process and no need to restart the process again, and hence the change requirements need to be documented and proceeds needs to be done as earlier. After all the change request is incorporated the client needs to perform the UAT and accepts the results. As the result is expected the client needs to perform sign off on paper and email which needs to be archived, for future reference.