Business Analyst III

Consults with internal customers and external vendors to capture agreed-upon business objectives and processes. Performs research and fact-finding to determine business requirements for development of end-user programs, operational procedures and support. Communicates these processes and their implications to technical and non-technical contributors to ensure that applications accurately meet business users' goals. Business Analysts create system requirements, collaborating with the design teams to determine that application, database, & other system impacts based on the requirements.

• Facilitate creation of Business Requirements following a traditional approach, or using the Business Process and Analysis (BPA) methodology as determined by the project sponsor
• Manage Scoring (approving) and Claiming processes with Business and Technology stakeholders to review and refine business requirements and use cases to ensure they are clear, concise and traceable; and to ensure business requirements will be satisfied by the appropriate teams / applications.
• Identify project stakeholders, risks and benefits of alternate designs; document assumptions; assess project impact of system changes to users, internal and external customers
• Develop System Requirements (SRQs), including process flows and use cases
• Conduct SRQ reviews with project stakeholders and document consumers to ensure completeness and adherence to business requirements
• Consult with internal customers, cross-functional team members and external vendors to capture agreed-upon business objectives and processes to define system requirements
• Update and map SRQs to Business Requirements in the Requirements Traceability Matrix (RTM)
• Review Architecture, Engineering and Application Development designs and QA / UAT test plans to ensure requirements are met and the RTM is updated as required
• Provide BA support for software testing and debugging plans to ensure requirements are met
• Provide status reporting for project progress, issues, dependencies and risks
• Level I: Typically performs smaller chunks of work or is one of many analysts on a project
• Work is reviewed with frequent process checks during larger projects
• Sphere of relationship and influence is primarily within the work team
• Level II: Where knowledge may not be readily available, incumbents at this level know how & where to research and what information is necessary to document
• Knowledge of the business may be deep in one functional area with surface understanding of other functional area.
• Sphere of relationship and influence is primarily within the team & with key stakeholders
• Level III: Proactively analyzes and documents solutions
• Identifies risks/pitfalls and articulates possible options
• Participates in business strategy & portfolio level discussions
• Knowledge of the business may be deep in one functional area with broad understanding of other functional areas.
• Knowledge sharing and mentoring of lower level team members is customary
• Sphere of relationship and influence is within team, with key stakeholders & with senior management
• May facilitate meetings
• Level IV: Proactive and avoids costly risks by providing optimal solutions
• Maintains an awareness of industry standards and advances knowledge base of functional areas.
• Serves as primary consultant to business owners for solutions in lieu of external consultation
• Participates and provides input in business strategy & portfolio level discussions
• Knowledge of the business is deep in more than one functional area with broad understanding of most functional areas.
• Knowledge sharing and mentoring of lower level team members is expected
• Sphere of relationship and influence is with all levels of the organization
• Identifies risks/pitfalls and articulates possible options
• Provides guidance to business and is considered a go to person for the business function
• Participates in vendor demonstrations, evaluations, and selection: may respond to RFP
• Facilitates meetings