Recordá que si te inscribiste a uno de nuestros eventos, ya estás registrado.
Si no recordás tu contraseña, hace click aquí para blanquearla.
The Business Analyst’s role at the Supervising Associate level is to confer with the stakeholders to understand, document, analyze and manage the requirements for the construction and testing of IT solutions. The Business Analyst facilitates the development process and confirms with supervisor that project deliverables are met according to specifications.
What are you going to do?
Consults with the business to understand the context of a project, identify the problem, current and desired future state, objectives, business needs and impacted user group.
Confirms the requirements are specified in a manner suitable for the intended audience and are understandable, unambiguous and capable of being implemented and tested.
Define how the requirements development will be conducted and can explain to others on the project team (i.e., elicitation, analysis, specification and validation).
Develops business, user and non-functional system level requirements in the form of Use Cases, UML and other similar structured requirements documentation.
Develops requirements Specifications in the form of gap analysis of requirements to COTS products
Develops requirements in the form of configuration requirements for COTS products
Experience in working as a BA in large & complex projects ($500K or more and 6 months or more in duration) which are broad in scope and dollar value, involving cross border team member
What do we need from you?
10 – 12 years of Industry Exp working in Large MNC
Min 5 years of experience as a Business Analyst
Excellent communications skills - strong verbal and written communication skills in order to develop and communicate project deliverables in a non-technical manner to end users.
Ability to work effectively with internal and vendors as well as across multiple geographies.
Good relationship building skills both within team, between teams, and across geographies.
Capable of utilizing formal business analysis methods and tools to govern and control programs.
Solid understanding of the following requirements models: Stakeholder Categories, Non-functional requirements, Configuration requirements, Gap Analysis, Actor Tables, Glossary, Context Diagram, Data Model, Class Model, Data Dictionary, Event Response Tables, State Diagrams, Business Rules, Decision Tables, Process Maps, Use Cases, and Activity Diagrams.