Job Title: Business Analyst / Scrum Master
- The BA would work closely with customers to understand their business model, requirements and translate them into software requirement documents.
- Should be able to understand client requirements, identify, define, document and communicate user and functional requirements for varied projects.
- Elicit requirements using interviews, document analysis, requirements workshops, surveys, site visits, business process descriptions, use cases, scenarios, business analysis, task and workflow analysis.
- Translate business requirement document to software requirement specifications according to standard templates
- Interact with the technical team to ensure that the requirements are understood correctly.
- Proactively communicate and collaborate with external and internal stakeholders to analyze information needs and functional requirements and deliver the following artifacts as needed:
- Functional requirements (Business Requirements Document)
- Use Cases
- Screen and Interface designs (Wireframes)
- Verify quality of development output by engaging in Functional Review and Testing.
- Successfully engage in multiple initiatives simultaneously.
- Work independently with users to define concepts and with direction of project/ product managers, system architects and product owners.
- Serve as the conduit between the customer community (internal and external customers) and the software development team through which requirements flow.
- Be the liaison between the business units, technology teams and support teams.
- Should be able to work with other BA Team members to complete a project from the requirement phase till the delivery phase, assuming different roles throughout the lifecycle of a project.
- Analytical skills, to critically evaluate the information gathered from multiple sources, reconcile conflicts, decompose high-level information into details, abstract up from low-level information to a more general understanding, distinguish presented user requests from the underlying true needs, and distinguish solution ideas from requirements.
- Facilitation skills, to lead requirements elicitation workshops.
- Observational skills, to validate data obtained via other techniques and expose new areas for elicitation.
- Writing skills, to communicate information effectively to customers, marketing, managers, and technical staff.
- Organizational skills, to work with the vast array of information gathered during elicitation and analysis and to cope with rapidly changing information.
- Interpersonal skills, to help negotiate priorities and to resolve conflicts among project stakeholders (such as customers, product/ project management, and engineering).
- Modeling skills, to represent requirements information in graphical forms that augment textual representations in natural language, including using modeling languages already established in the development organization.
- Good communication skills.
- Fast learner and open to new ways of doing things.
- Innovative in nature.