IT Business Analyst

PRIMARY RESPONSIBILITIES:
The IT Business Analyst primary responsibility will be gathering business requirements and documenting requirements for business approval. The specific day to day job responsibilities will include, but are not limited to:
1. Requirements planning.
2. Requirements elicitation. 3. Create excellent documentation (e.g., functional requirements, non-functional requirements, user stories, etc.) that can easily be understood by highly technical outsourced or distributed teams
4. Selecting the appropriate elicitation technique to efficiently identify critical requirements.
5. Analyzing and refining business, functional, and operational requirements.
6. Asking the right questions using interviewing templates developed specifically for business analysis elicitation.
7. Quickly understand technical vision and align interactions, meetings, etc., with steps to achieve future state.
8. Lead requirements gathering sessions with business leaders; facilitate stakeholder process to find common ground on business needs, process requirements, and prioritization and differentiate needs versus wants, etc., throughout each session.
9. Responsible for tractability matrices to ensure that all project and program requirements are delivered through business processes and software objects.
10. Define testing objectives and verify requirements are testable.
11. Build strong relationships with project stakeholders and utilize these relationships to meet sponsor project and program objectives in a timely manner.
12. Anticipate issues, think proactively, and use critical thinking skills to plan stakeholder elicitation sessions.
13. Effectively communicate business needs, organizational changes, etc., across the team (e.g., business leaders, service line technical solution architects, etc.); ensure strong understanding from all team members.
14. Responsible for working with the IT Project Manager on communications with internal and external sources. Must be able to support multiple service line leaders and projects as allocation needs change for the organization.
15. Interested in and able to work as an individual contributor.
16. Experience with SAAS based applications and how to elicit requirements to meet the technology needs.
17. Experience with SAP applications is nice to have