Senior Business Systems Analyst Resume
SUMMARY
- Information Technology Professional with over 7 years of experience as a Business Systems Analyst with more than 19 years focusing on business process, analysis, risk, and control.
- Recent experience has been in business analysis, waterfall and agile.
- Extensive experience working with business partners and technical leads and developers utilizing Microsoft Office tools and Software Development Life Cycle (SDLC).
- Experience with strategic and tactical engagements in the Retirement Services industry.
- Extensive knowledge in Asset Management, IT project planning, testing, problem solving and implementation.
- Excellent communication skills, both written and verbal, with the proven ability to communicate to peers, business partners, management, technical leads, and developers.
- Directly responsible for facilitating requirement work sessions, gathering business requirements, coordinating testing efforts and presenting both requirements and technical documents to key stakeholders (Upper Management, SME’s, Quality Assurance Analysts, Developers).
- Ability to interact with teams and executives at all levels and across different departments.
TECHNICAL SKILLS
Programming Languages/Tools: COBOL, JCL, VSAM, SAS, DB2, TSO/ISPF, Xpeditor, ChangeMan, Syncsort, File - Aid, IBM Utilities, ClearQuest, Rational RequisitePro, SharePoint, Clarity, VersionOne, SQL, Extreme Dialogue, CICS and Jobtrac
Software/Systems/Databases: Microsoft Office Suite (Excel, Word, Access, PowerPoint, Outlook, Visio), OmniPlus, OmniStation, Quality Center, WinSQL
Methodologies: Waterfall, Agile, SDLC
PROFESSIONAL EXPERIENCE
Confidential
SENIOR BUSINESS SYSTEMS ANALYST
Responsibilities:
- Gathered requirements and created user stories as a Story Author in Agile Scrum Teams for multiple financial applications.
- Collaborated with the Product Owners and developers for the development of the stories
- Facilitated grooming sessions with the Agile Team, including the Scrum Master, Product Owners/Stakeholders, Quality Assurance Analysts and Developers.
- Stepped in and ran daily huddles upon Scrum Masters absence
- Managed the user stories in Version One software.
- Gathered and documented business and technical requirements using Sharepoint
- Worked in the waterfall methodology gathering and writing Technical Requirements Document.
- Facilitated extensive meetings to walk through the documents.
- Tracked time and forecasting in Clarity
Confidential
BUSINESS SYSTEMS ANALYST
Responsibilities:
- Provided analytical and technical expertise gathering IT requirements for the DOL regulated Participant Fee Disclosure.
- Worked with Product, Operations and IT Developers to write the mapping of fields from the SQL Database to the Disclosure Template.
- Wrote SQL queries to assist with testing and implementation of the Participant Fee Disclosure
- Gathered technical requirement and wrote the Technical Requirements Documents for the many enhancements that were made to the fee disclosure.
- Collaborated with the Business partners, third party vendors and software developers to ensure technical requirements aligned with business requirements.
- Provided support in the implementation of the Participant Fee Disclosure during release weekend, providing support and attending status meetings.
Confidential
BUSINESS SYSTEMS ANALYST
Responsibilities:
- Collaborated with Business Partners to gather and document Business Requirements for multiple projects
- Worked with the software developers to document an Internal User Guide, Release Notes and Power Point presentation for the projects I worked on.
- Performed SQL queries and assisted with testing the project.
- Utilized SharePoint to track all documentation for the projects and Clarity to track time.
- Facilitated meetings to walk through the documents with all key stakeholders.
Confidential
BUSINESS SYSTEMS ANALYST
Responsibilities:
- Gathered IT Requirements for the technical design and project related documentation for development/enhancement of the Payroll Feedback File (Service that provides the data Sponsors or Payroll Vendors need to update their payroll system with Participants’ plan-related payroll deductions).
- Worked with technical leads during implementation to help resolve issues
- Assisted in the technical design and project related documentation for development/enhancement of Automating the 5500 Process and Schedule C Process.
- Defined business and system design requirements by facilitating user meetings, interviewing users and developers, and researching and resolving issues.
- Analyzed and translated business needs and requirements into technical requirements and use case documentation and presented design solutions to business, end user, and technical teams.
- Followed the business requirement's documentation process utilizing the appropriate tools to track the progress of projects by utilizing Clear Quest, Rational Requisite Pro, SharePoint and Clarity.
Confidential, Iselin, NJ
Systems Analyst and Development Specialist
Responsibilities:
- Responsible for the Trading process between the trades that came in from UPS and transmitted to Mellon Bank.
- Partnered with the Business Analysts and Development Managers to map the data elements and design the flow of the trading process that is currently being utilized.
- Coded new Trading Program in COBOL to create financial transactions to send to Mellon. This was completed within a minimal time frame with incomplete requirements provided.
- Implemented the process to assure trades sent on a timely manner saving Prudential money from any slippage that might have occurred due to late trades.
- Analyzed and designed the standards of Plan / Participant Correspondence for all of Retirement Services.
- Coded programs to create extract files containing participant and plan information from Omni to be fed to DIALOGUE.
- Developed template to be used for all correspondence to plan and participants in DIALOGUE.
- Created all JCL's to produce letters in our printing facility and our OnDemand system.
- Implemented the new letters and twilighted the old jobs and programs that created the old letters, saving mainframe costs and saving DASD space.
