SUMMARY:

• 6 years of experience supporting IT projects in the role of Business Analyst and Data/Technical Analyst
• Experience supporting Data Warehousing (BIDW), SFT (File Transfer) and Web projects as a Technical BA
• Worked as a Consultant for Business Process Analysis and Customer Satisfaction Measurement for Global Corporate Accounts
• Sound knowledge of regulatory Financial reporting, Credit card Collections, E2E Credit card processing, Cost, Planning and forecasting
• Experience in creating documents & deliverables projects following Agile and waterfall methodology
• Worked closely as a project coordinator with various project teams like Development teams, QA teams and Business to meet project objectives
• Experience in writing User stories, Requirements gathering, Feasibility studies, Scope Documentation and Change requests
• Experience in interacting with the end - users and facilitating cross-team JAD sessions
• Experience in creating Requirement Use Case Specification document and Functional specification Document(FSD)
• Excellent in preparing Activity diagrams and Use cases for the Business process flows
• Experience in assisting QA team and Business in formulating Test Plan, Test Scripts and Test Cases based on the Design Document and User Requirement Document for the Integration, Regression, Functional, Performance, and User Acceptance Testing (UAT)

PROFESSIONAL EXPERIENCE:

Confidential, Phoenix, AZ

Business Systems Analyst

Responsibilities:

• Document user stories for specific data requirements and business rules
• Facilitate user story grooming session, sprint planning sessions, daily stand up
• Created business mapping document and map-gap analysis for different reports
• Perform Business Analyst role in various phases of the project and supported project manager
• Identify data needs for report from source systems
• Coordinated meetings with Source system for business requirements
• Coordinated meetings with Business to create business mapping documents for attribute level mapping, business rules and transformations
• Create source to target mapping documents, perform gap analysis and plan mitigations
• Coordinate with business to create Business and Technical data quality rules (BDQ and TDQ)
• Resolve data issues with upstream and downstream systems

Tools: used: Rally, Netezza, Oracle, MS Office, Clarity, SharePoint

Confidential, Phoenix, Arizona

Business Systems and QA Analyst

Responsibilities:

• Setting up and facilitating requirement review, defect review and triaging meetings
• Facilitated Product defect review and Product enhancement meetings
• Taking custom requirements for enhancements of the Web page/tool and doing walkthrough for the Tech teams/developers on the requirements/enhancements
• Defining the metric used on the KPI’s dashboard.
• Responsible for Onboarding client on PI tool which includes activities like Creating client hierarchy, Ingestion of card & Travel data in base tables.
• Conducting UAT on behalf of Business users before client go-live date, tracking Pre-UAT defects & conducting RCA and Publishing RCA report
• Managed and validated defects logged by Product development team & developers
• Data validation in development and Production environment in Hadoop Hive tables using SQL queries
• Sanity check of PI Production space after weekly update
• Validated page wise look and Feel of the PI tool for every Client Onboarding
• Managing Offshore QA team to conduct regular QA and testing efforts, resolved their queries testing streams including data setup
• Coordination of Testing Effort for SIT, UAT and regression testing
• Creation of the traceability matrix to illustrate the trail of criticality throughout the requirements and ensures that requirements designated as critical are not tied to a higher-level stakeholder needs that has been deemed as a lower priority

Tools: used: Hadoop Hive, SQL, SSIS, JIRA, MS Office, Clarity, SharePoint, Equip.

Confidential, Phoenix, Arizona

Business Systems Analyst

• Project was to set up the File Transfer capability for Confidential (AEGBT). After the split of Confidential and its Global Travel business, AEGBT is to set up its own File Transfer mechanism moving away from the integrated Confidential File transfer process. Amex File exchange is the backbone of Amex business for exchange of files between its internal and external customers.
• Identified COTS product for file exchange needs of AEGBT. This included comparing available products in market and selection procedure based on pre-defined AEGBT requirements.
• Responsible for documentation and approval process of the final product based on the analysis and suitability of the product.
• Managed On-boarding of vendor in AEGBT. This included Risk assessment, SAR process and legal assessment for the vendor product.
• Creation of the overall Business Requirement document and Test case document, utilized As-Is documents to create the BRD.
• Identified profiles for migration, conducted sessions with Users to identify their remediation strategy.
• Used Transmitter Profile and Tracking and Monitoring tool to check he existing file transfer set-up and specific details such as File names, exchange frequency and Source/Destination information.
• Identified the environment needs for the new product in consultation with the vendor.

Tools: used: MS Office, TP and TM (SFTP profile systems), Clarity, SharePoint, Equip.

Confidential

Business Analyst

Responsibilities:

• Creation of BRD for the customization requirements on the basis of business objectives
• Interaction with the end-users and facilitated cross-team JAD sessions
• Creation of use cases and activity diagrams for AS-IS and TO-BE process flows
• Creation of detailed technical requirements with the help of development team
• Worked closely with project manager on all phases of SDLC using waterfall methodology
• Assisted QA team in creating Test plans and test cases
• Coordination of Testing Effort for SIT, UAT and regression testing
• Creation of the traceability matrix to illustrate the trail of criticality throughout the requirements and ensures that requirements designated as critical are not tied to a higher-level stakeholder needs that has been deemed as a lower priority

Confidential

Business Analyst

Responsibilities:

• Creation of Business and Technical Requirement document (BTRD) for project releases.
• Creation of Test Plan and Test Cases for System Testing of all components of the monthly release and special projects.
• Coordinate the Testing Effort for SIT and UAT.
• Recognize patterns in requirements and categorized them appropriately
• Created the FDD (Functional Design Document.)
• Created the traceability matrix to illustrate the trail of criticality throughout the requirements and ensures that requirements designated as critical are not tied to a higher-level stakeholder needs that has been deemed as a lower priority.
• Used the Use Case model to include the business rules and descriptions of system behavior.

Confidential

Business Analyst

Responsibilities:

• Creation of Business and Technical Requirement document (BTRD) for project releases.
• Creation of Test Plan and Test Cases for System Testing of all components of the monthly release and special projects.
• Coordinate the Testing Effort for SIT and UAT.
• Recognize patterns in requirements and categorized them appropriately
• Created the FDD (Functional Design Document.)
• Created the traceability matrix to illustrate the trail of criticality throughout the requirements and ensures that requirements designated as critical are not tied to a higher-level stakeholder needs that has been deemed as a lower priority.
• Used the Use Case model to include the business rules and descriptions of system behavior.

Confidential

Business Analyst

Confidential

Responsibilities:

• Creation of Business and Technical Requirement document (BTRD) for project releases.
• Creation of Test Plan and Test Cases for System Testing of all components of the monthly release and special projects.
• Coordinate the Testing Effort for SIT and UAT.
• Recognize patterns in requirements and categorized them appropriately
• Used the Use Case model to include the business rules and descriptions of system behavior.