LEAD BUSINESS ANALYST

Responsibility involves acting as a liaison between the business/end users and IT systems development teams for business needs requiring IT based solutions including:
Identifying and analyzing business needs, conducting requirements gathering, and defining scope and objectives
Making recommendations for solutions or improvements to business processes that can be accomplished through new technology or alternative uses of existing technology
Researching business requirements and documenting the relationships between the components of the application system (i.e., end users, business processes, data, applications, and devices) Translating business requirements into application requirements

Engineering graduate, MCA, etc Experience: 5-8 years

1. Requirements Elicitation and Analysis:
a. Strong elicitation skills are a must have in defining requirements for the success of a project. Elicitation skills like: BA plans to meet the stakeholders in one-on-one sessions (or) in a requirements workshop (or) remotely (or) conduct JAD sessions; the BA needs to know how to select and implement techniques to accurately and efficiently identify the needs of the business/ business case.
b. Establish and communicate the scope for eliciting requirements for a project to internal stakeholders (technical architects, project manager, program manager) and to external stakeholder (customer).

2. Requirements Detailing:
Once, the requirements are analysed the BA should be able to perform the following:
a. Define high-level functional requirements and NFR s.
b. Prepare workflow diagrams.
c. Define UX. Tools like the following can be used to define the UX: Balsamiq, MS Visio etc..
d. Detail requirements: Based on the project needs either define Epics and detail User Stories (or) define User Case Scenario s.
e. Prepare a detailed data-dictionary.

3. Requirements Sign Off & Walk-throughs:
a. Get all the requirements approved and Sign Off by the customer based on the timelines defined.
b. Provide walk-through s to the development team and QA team.
c. Be available to the internal team in clarifying queries on requirements as and when required.

4. Link between internals team and stakeholders:
a. The BA needs to form a strong link between the internal team (Dev, QA) and the stakeholders.
b. Triage between the internal team and stakeholders in providing clarifications to the queries that the team has on requirements.

5. Manage Requirements:
a. BA needs to manage the complete application requirements, requirements backlog.
b. The approved and latest requirements must be available for the team to consume for development and testing.
c. Any updates to the requirements must be communicated to the team immediately.
d. Manage the change requests logs. Provide the T-Shirt sizing of the requirements and work with the architects in providing the efforts change.

6. Perform smoke test/ UAT:
Once the QA certifies that the build is stable, the BA needs to perform smoke test and UAT in order to see if the high-level and important functionalities of the application meets as per the requirements approved.