Author Topic: BA Role  (Read 1006 times)


  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: BA Role
« Reply #15 on: May 19, 2020, 10:13:23 am »
A Business Analyst would typically perform the below traditional activities for a software development project:

1.Represent stakeholders
2.Scope the system, Elicit project requirements, especially the business requirements.
3.Write the project requirements in a clear, concise manner.
4.Translate business needs
5.Translate technical issues
6.Manage the project requirements.
7.Lead requirement reviews.
8.Create and maintain analysis or domain models for the requirements.
9.Work with the test team to make sure the tests adequately cover the requirements.
10.Run the User Acceptance tests.


  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: BA Role
« Reply #16 on: May 30, 2020, 11:25:37 am »
1.   BRD, FRD, SRS , RTM, UML diagrams
2.   End user manuals
3.     Wire framing screens


  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: BA Role
« Reply #17 on: June 04, 2020, 04:59:53 am »
A business Analyst works along with the technical team and acts as a liaison between stakeholders of the client and the technical team.
Main Responsibilities :
Client interaction
Ownership of Requirements

These are the technique used by BA in a project:
Requirement Gathering
Handling change request
Facilitating  UAT

« Last Edit: June 04, 2020, 05:31:36 am by 1202894803 »


  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: BA Role
« Reply #18 on: June 06, 2020, 03:41:05 pm »
BA deliverable's in agile:
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


  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: BA Role
« Reply #19 on: June 18, 2020, 03:30:55 pm »
Scrum Business Analysts complement and support the PO in a number of ways:

They carry the brunt of the Requirements Elaboration effort, while Still deferring to the PO for final decision making.
They elaborate Acceptance Criteria for user stories prioritised by the PO.
They (usually) bring good product and systems understanding, and advise the PO on Requirements Analysis, Scope, MVP, User stories and Prioritisation.
They work with extended stakeholder teams to understand and analyse any customisation needs.
For instance, if you are deploying a mobile app to a number of markets where your company has a presence, the BA would work alongside the PO to discuss market specific requirements and practices that need to be catered for before the product launch. Typically, I?ve seen a PO appoint Lead BAs to support customisation and implementation of a product in each of their markets.
During Sprints, BAs provide everyday Requirements and Solutions support to the Scrum team and step in for the PO where the PO isn?t immediately available.
Scrum BAs take on the additional System Analyst dimension, amalgamating (rightly) two key Analysis functions (more on this later).
Scrum BAs regularly conduct Analysis into a number of activities including Sprint Planning and Backlog Grooming, and recommend next actions and decisions for the PO?s approval.
A lot of the time, Scrum BAs go on to become Product Owners ? given sufficient product ownership and involvement and business and market acumen among other factors.