Shashank Vyas

• Mar 31st, 2015

 

Key responsibilities of Business Analyst differ from company to company. In few companies business analyst is responsible for both pre - sales and post sales activities whereas in larger structured firms activities of BA is limited to post sales activities.
BA is responsible for collect business requirement of the client and prepare BRD in layman terms AS IS and gap analysis, further he is also responsible for preparing Software / system requirement specification for the developer and function specific document.
His role also entails functional testing, UAT, change and risk management,many a place managing project, project release and training.
BA should also posses SQL knowledge to check the data updation at both front and back end.

Himanshu Maindola

• Apr 2nd, 2015

 

Client Interaction
Ownership
Process (Re) Engineering.

pankaj yadav

• Apr 14th, 2015

 

Extract requirements: Requirements play a key part in engineering IT systems. Incomplete or improper requirements usually lead to project failure. A business analyst determines a project’s requirements by extracting them from business or government policies, as well as from current and future users, through interaction and research.

Anticipate requirements: Skilled business analysts know how quickly things change in the dynamic world of IT. Baseline plans are subject to modification, and anticipating requirements that will be needed in the future or that have not yet been considered is essential to successful outcomes.

Constrain requirements: While complete requirements are essential to project success, the focus must remain on core business needs, and not users’ personal preferences, functions related to trends or outdated processes, or other non-essential modifications.

Managing requirements: Typically, a formal requirements presentation, review and approval session occurs, where project schedules, costs and duration estimates are updated and the business objectives are revisited. Upon approval, the business analyst transitions into requirements management activities for the rest of the IT solution life cycle.

System and operations maintenance: Once all requirements have been met and the IT solution delivered, the business analyst’s role shifts to maintenance, or preventing and correcting defects; enhancements, or making changes to increase the value provided by the system; and operations and maintenance, or providing system validation procedures, maintenance reports, deactivation plans, and other documents, plans and reports. The business analyst will also play a major role in analyzing the system to determine when deactivation or replacement is required.

Pooja

• Jun 12th, 2015

 

Requirement elicitation, Client interaction, stakeholder analysis, Requirement traceability, Deliverable ownership, approval of requirement package