1Ans. Normally, for certain duration of a project, the percentage of BA taking the details and knowing about the project from customer is 12 to 16 percent i.e. if the project duration is 1 year, the time taken by the Business Analyst knowing the details of the company, gathering the requirements and knowing about the company in detail, it takes about 2 to 3 months. So, in the first stage, the Business Analyst asks about the requirements from the customer i.e. Requirement Gatherings. It will be in this manner: –
- Knowing who is the correct stakeholder who can give details of the company in brief and proper manner.
- Once we find the stakeholder, we have to do interaction with the customer or client by conducting Brainstorming sessions and doing document analysis by making the BRD (Business Requirement Document).
- Again asking the questions i.e. questioning the questions till we get direct answers from the client.
- After taking all the requirements, we sort the requirements.
- Then prioritize requirements by using various analysis techniques.
- Validate requirements by using FURPS technique.
After this is done, then we do Requirement Analysis by: –
- Drawing UML Diagrams.
- Preparing functional requirements from Business Requirements and architects will do technical requirements.
- In this way we prepare SRS (Software requirements Specifications) which consists of Functional and technical requirements.
- Taking SRS and taking sign off from the technical team as it is the first legal document signed between Business team and technical team.
- Before design phase starts, we have make RTM (Requirement Traceability Matrix) and knowing how requirements are dealt in each phase of development life cycle till UAT.
After doing Requirement Analysis, then it goes to Design Phase. In this phase, it will be like: –
- From Use case diagrams, test cases are prepared.
- After this, the test cases along with use case diagrams are discussed with Client on design and solution documents. If the customer is okay with the use case diagrams and test cases, then this will be moving forward to next step.
- Then the RTM is updated and from this RACI Matrix is obtained to know who is responsible, accountable, consulting and informed.
- From use case diagrams, solution architect recommends architecture for IT solution.
- The DB architect uses persistence class and comes up with ER Diagrams.
- The designer will look into transient class and design will fall possible to IT solution.
Then from Design, it goes into Development and Testing Phase. In this,
- We will be organizing JAD (Joint Application development) sessions.
- Clarifying queries during development.
- Referring diagrams and consulting BA and clarifying Doubts.
- Updating End user Manuals.
- Conducting meetings with technical team and client for participation.
After this is over, then it goes to UAT (User Acceptance Testing). In this: –
- Preparing test cases.
- Performing high level testing.
- Preparing client for UAT.
- Test data required from client.
- Update end user manual.
- Updates RTM.
- Take signoff from Client in Project Acceptance Form.
If these all are done without causing any disturbances like:- not telling the requirements in detail, no involvement of client during the project, involvement of negative stakeholders who try to stop the project, absence of client during the meeting, clients asking for change request as and when required and concentrating on multiple projects rather than concentrating on ongoing project. Then as a Business Analyst, I can say that Project is on schedule to meet the deadline.