BA Role

[12228280305]

The BA role is all about ensuring that each project delivers the value the business needs and expects. Actively participating in planning for and running User Acceptance Testing is an important way for the BA to ensure that value is indeed delivered.

[12221267604]

The BA role is all about ensuring that each project delivers the value the business needs and expects. If the it is not according to  the requirements of client, BA will communicates with tester.

[12209232002]

 1.Recognize the Business Needs
An Agile BA holds discussions with stakeholders to understand their requirements and their vision of the product. This is then translated into business needs and communicated to the team members to make them understand the expectations of the project.

2. Analyze the Business Domain
An Agile BA needs to analyze the whole system in detail - from the first iteration to the release phase of the project. They work closely with the development team to understand the initial requirement of the project, the scope of the project, and also identify automation areas of the project.

Post Graduate Program in Business Analysis
In partnership with Purdue UniversityVIEW COURSEPost Graduate Program in Business Analysis
3. Stock and Groom the Product Catalog
Stocking the product backlog refers to establishing user stories that represent the overall scope of the project. Agile BA help the product owner establish user stories from the requirement models created during business analysis.

Grooming the product backlog refers to maintaining the product backlog so that it does not become a burden on the product owner and the team. Agile BA achieve this by considering purpose, organizing and prioritizing user stories, and splitting epics into user stories.

4. Helps Team Understand the Big Picture
An Agile BA helps the team to get a better grasp of the project and where it fits within the organizational strategy. This can be done by facilitating a number of discussions such as:

What business processes should be created, eliminated, or revised?
What stakeholders are involved in the project?
What information should be tracked?
What policies and rules should be followed that affect business behavior and decisions?

[12212216902]

What is BA role in Change Request?

BA has to evaluate the resources that will be incurred for the change i.e., time, staff, money. BA has to get an Approval or rejection of the change before he can actually implement the Change Request. He has to get the approval from the change manage or the project manager to move further.

[12230256704]

REQUIREMENT GATHERING
DOCUMENTING REQUIREMENT
MODELLING REQUIREMENT
COMMUNICATING REQUIREMENT
TRACK REQUIREMENT
HANDLE CHANGE REQUEST
USER ACCEPTANCE TESTING

[12228258603]

?   Liaising between the IT department and the executive branch.
?   Acting as an information source and communicator between business branches.
?   Understanding strategic business needs and plans for growth.
?   Enhancing the quality of IT products and services.
?   Analyzing the design of technical systems and business models.
?   Utilizing IT data for business insights.
?   Analyzing business needs.
?   Sourcing and implementing new business technology.
?   Finding technological solutions to business requirements.
?   Producing reports on application development and implementation.
?   Running A/B tests and analyzing data.
?   Analyzing data to inform business decisions.

[Harshal Dagaji Patil]

What is the difference between change request and enhancement and define both?

[Harshal Dagaji Patil]

What is the role of BA in Design, coding and testing phase of waterfall methodology?

[12221277305]

User Acceptance Testing (UAT) is a phase in the software development life cycle where the intended users of a system participate in validating that the solution meets their needs.
User Acceptance Testing is conducted to assess if the system can support day-to-day business and user scenarios and to ensure the system is sufficient and correct for business usage.

1. BAs understand the functionality the system is supposed to deliver and as such, have the knowledge needed to validate the system (confirm whether the solution meets business needs or not). The fact that a system has been built to specification does not make it automatically acceptable.
2. Getting involved in UAT presents an opportunity for the BA to confirm the correctness of previously elicited requirements and improve on future projects.
3. Being part of the UAT session will help the Business Analyst understand the rationale for any proposed change, suggest the most appropriate way to meet the business need.
4. When BAs who have a first-hand knowledge of system functionalities are involved in UAT, they are able to support training efforts prior to UAT and answer users' questions during test sessions.
5. As part of solution validation, the BA may be brought in to support the team in assessing the severity of defects, their impact on the business, which defects must be resolved before go-live and what can be done to mitigate the risks of the defects that cannot be resolved.
6. Business Analysts are involved in determining the set of requirements the solution must meet to be considered acceptable. In an ideal world, users are expected to write their own test scripts but in reality, BAs usually have to support this task or write the test scripts themselves.