Author Topic: BA Role  (Read 4158 times)

12107163810

  • Global Moderator
  • Newbie
  • *****
  • Posts: 21
Re: BA Role
« Reply #45 on: March 21, 2022, 10:23:29 am »
Creating a detailed business analysis, outlining problems, opportunities and solutions for a business.
Budgeting and forecasting.
Planning and monitoring.
Variance analysis.
Pricing.
Reporting.
Defining business requirements and reporting them back to stakeholders

12120171211

  • Newbie
  • *
  • Posts: 21
Re: BA Role
« Reply #46 on: March 29, 2022, 03:09:57 pm »
The role of a BA as a product owner and a team member. This is critical to highlight how a BA finds a place in agile projects. The BA at times can become a product owner himself and many times they just work as a team member as well.

12130164810

  • Global Moderator
  • Newbie
  • *****
  • Posts: 21
Re: BA Role
« Reply #47 on: April 16, 2022, 01:48:37 am »
BA role is same either in Agile or Non-Agile projects in the form of activities and mentors the Development and QA teams in all phases.
Product Owner is primarily responsible in Agile projects but BA plays a major role.
BA is primarily responsible in Non-Agile projects.

BA in non-Agile projects:

Activities:
1.   Gathering/ eliciting /fine tuning the requirements
2.   Conducts requirements review/planning meetings , walk through sessions, stakeholder interviews
3.   Mentor the Dev and QA teams in all phases
4.   Participate in Functional testing, tracking requirements and releases
5.   Prepares end user manuals and UML diagrams like use case, activity, flow, sequence
6.   Handles the CRs

Deliverables:
1.   BRD, FRD, SRS , RTM, UML diagrams
2.   End user manuals
3.   Mockup screens


BA in Agile projects:

BA is considered as a Team Member in Agile projects and closely work with Product Owner to make sure project is on track with the help of BA activities.

Activities:
1.   Gathering/ eliciting /fine tuning the requirements
2.   Conducts requirements review/planning meetings , walk through sessions, stakeholder interviews
3.   Mentor the Dev and QA teams in all phases
4.   Participate in Functional testing, tracking requirements and releases
5.   Prepares end user manuals and UML diagrams like use case, activity, flow, sequence
6.   Handles the CRs

Deliverables:
 BA prepares below docs if the project is implementing from scratch level.
1.   BRD - as per Product Owner need at project initiation phase
2.   FRD - its replaced by Product backlog
3.   SRS - as per Product Owner need at project initiation phase
4.   RTM - its replaced by Scrum tool
5.   UML diagrams as per client need at project initiation phase, very less possibility.
6.   End user manuals
7.   Mockup screens

12117192212

  • Global Moderator
  • Newbie
  • *****
  • Posts: 21
Re: BA Role
« Reply #48 on: April 30, 2022, 11:12:32 am »
Business analyst is a person who works along with the technical team & acts as a liaison between the stakeholders of the client & the technical team. He is the face of the technical team to the client & all client communication will happen through the business analyst. He will elicit, analyze  communicate & validate the requirement changes to the business process & policies & information system in the existing business proves of the client. The business analyst understand the business problems & recommends solution that enables organization to achieve it's goals.

Prime responsibilities:-
1.Client interactions.
2.Ownership requirement.
3.Process re-engineering

Roles:-
1.Gathering requirement using the elicitation techniques.
2.Documents the requirement using the industry standards.
3.Model the requirement using UML.
4. Communicates the requirement to the technical team.
5.Track the requirement during the development stage.
6.Handle the change request.
7.Facilitates the UAT(User acceptance testing).

12106197412

  • Global Moderator
  • Newbie
  • *****
  • Posts: 20
Re: BA Role
« Reply #49 on: May 10, 2022, 04:25:39 pm »
* A business analyst is the first point of contact for the client.
* Client provides his requirements and business analyst analyzes it.
* It is very important for a business analyst to understand the requirements clearly as the client will contact him/her for any query or update.
* The business analyst discusses the requirement with the technical team. This gives a clear high-level understanding of the requirements.
* On the basis of this understanding, business analyst starts drafting project scope.
* Once the project scope is finalized, it is provided to the client with effort estimation.
* A business analyst should always recommend the client to take a call/meeting with him/her and the technical team, for discussing the sent scope document.
* Once the client finalizes the project scope, that means the project is on the floor and development work will be started on it.
* Before that, the business analyst takes a kick-off call with the technical team as well as the client.
* Then the business analyst prepares the SRS document the explains each and every module of requirement in detail. It includes all the functional and non-functional requirements. Then project development starts.
* During project development, the business analyst is responsible for managing the documentation work. This includes documents like Project Plan, Meeting MOMs, etc.
* The business analyst is responsible for daily or weekly meetings with the team as well as with the client.
* The business analyst is responsible for performing the UAT.
* The business analyst is responsible for project health inspection and review.
* When the project gets completed, the business analyst is responsible for doing a retrospective meeting and making a closure report for the project.