Manisha Sabat

Hilton Localization Project (PEPLL) – Hilton is creating a new PMS called PEP. This new system will eventually replace OnQ and Opera. The project is to capture the legal requirements for the global countries (except USA and Canada) to ensure PEP is developed in compliance with the legal requirements.

· Send out Localization document template to a country and document all the requirements for the country. The requirements captured are General Information , Currency Information, Payment Methods, Deposits, Room Taxes, General Taxes, Invoice Requirements, Extract Files, Reports, Additional Guest Data, Registration Cards, Invoice Layout and all the document samples

· Working on the following countries to capture requirements for each region finance managers: Hong Kong, India, Italy, Luxembourg, Sweden, Finland, and Bosnia

· Write user stories and epics documenting the functional, non-functional and technical user stories

· Create user story and add information to the following fields: Priority, Functional Impact, User Permission Group, Feature Overview, High Level Business Impact, Applies to: Module (ex, Front Desk, Reports, Property settings), Account Type (ex, Reservation, House Account, Group Master, AR Company Etc.), System (HRCR/PCRS), and Country (Global or specific country), Current Business Flow, Acceptance Criteria, Accessibility Requirements, Impact Analysis (Functional & Technical Impact), User Permission Required, Property/Country Config required, Other Considerations (Assumptions, Unknowns (User Related & Technical), Change management, Training, Pilot Required.

· Create bugs and add information to the following fields: PRB #, INC #, Applies to (Module, Account Type, System, Country), Property Code, Steps to Reproduce, Current Behavior Expected Behavior, Accessibility Requirements, Impact Analysis (Functional & Technical), Able to Reproduce in Hotfix/stage environments. Splunklog, JSON files, Workaround, Other Considerations

· Sync up call with EQAC (Quality Engineering) team to review all the bugs created during the sprint and prioritize the bugs. The prioritized bugs are slated to be fixed during the sprint and the low priority bugs are moved to the backlog.

· Review the Refined tickets (Refined tickets are added with technical details such as if a story or bugs require Configuration, User permission, Code or database change or API changes) and clarify information if required.

· Review the tickets to add “fixbug” labels to all the bugs in the sprint and “Pilot validation” for all the stories in the sprint before the start of the sprint.

· Review tickets to add Configuration or User permission labels for all the stories/bugs towards the end of the sprint and assign it to one core epic so that all the tickets are worked together for configuration/user permission.

· Prepare Invoices (Excel) and Registration Card (PowerPoint) mock-ups for different countries.

· Present the requirements in the Pre-Refinements sessions and clarify any issues or concerns regarding the requirements.

· Collaborate with the countries Finance advisor to understand the requirements and get a sign off for each country

· Present the Sprint Demo in the SIT (Test) environment to all the Pods (teams) at Hilton

· Collaborate with different teams such PEPR (Core Team) & Faux (UX team) to review requirements that can affect localization teams or vice versa.

Environment: SDLC, Agile/Scrum, MS Office, Microsoft Excel, JIRA, Visio, Confluence, PEP PMS Application. Lobby Application

MGP-Marriott Growth Platform Hotel Operations- Part of SHIJI PMS (Property Management System)/ Hotel Operations Integrations Team(HINT)– Marriott has legacy Marriott PMS landscape systems (FOSSE, FSPMS, OPERA, Lightspeed and other PMS systems in smaller hotels) and currently is in the process to implement new PMS’s for the entire Marriott operations. The new PMS’s systems and enhancements are ACRS- Reservations source of truth, Oracle Opera Cloud, Agilysys Stay, Integrations (HINT), SHIJI, Single Pane of Glass (SPOG), Auto Room Assignment and PMS C&D. I worked for SHIJI PMS systems to analyze PMS requirements, document functional and non-functional requirements, dependencies on other impacted systems and currently part of the Integration team (HINT) platform. ACRS which is being developed by Amadeus will be the Reservation source of truth and all the PMS will be integrated with the ACRS to get updated reservation information.

· Documented all the functionalities of Lightspeed PMS application to understand the current functionality for each domain.

· Initially worked in Agilysys team to document notes, screenshots, follow up items for the BRM’s in JIRA

· Worked in Engineering/Integration team to document technical user stories, facilitate meeting between engineering and PMS’s team to discuss the technical aspects of the functional requirements.

· The XPMS (Opera & Agilysys) will event out the events to the event hub and worked on distinguishing which events are evented out by this application.

· The XPMS events are based on the use cases and the data will go through data adapters or domain services. This data will be converted into MMF format and will be posted to the event hub. The other applications will get updates from the event hub through the API services. The XPMS will not consume any events from the event hub.

· Worked on understanding the architecture flow of PMS and FOLIO ODS. Data flows from the PMS and will be converted into the MMF (Marriott Messaging Format) and will be passed to the Event Hub where the downstream systems can consume the events. Folio ODS is a data warehouse where all folio transactions posted in PMS will be stored for downstream systems to consume. Downstream systems can determine if they want to consume data from the event hub or the folio ODS based on their architecture or preference.

· Mapped requirements for each PMS BRM’s to technical requirements for APMS, Agilysy and Opera and made updates and changes accordingly.

· Work in Collaboration with the GO team (Business) to validate requirements and write epics and user stories for SHIJI & HINT

· Work in collaboration with different PMS’s such as Agilysys Stay (STAYPMS), Oracle Opera Cloud (OCPMS), PMS Conversion & Deployment (PMSCD), SHIJI PMS (SPMS), SPOG (Single Pane of Glass), ARA (Auto Room Assignment) and MGP Point of Sale (MGPPOS) to understand and document dependencies.

· Facilitate vendor discussions and deep dive activities such as functional and non-functional requirements, systems and security discussions and different impacted systems.

· Document all the BRM’s (Business Requirements Matrix) in JIRA that are being reviewed by Global operations and Continental stakeholders which are the functional requirements not fulfilled by the vendor company. These BRM’s by each vendor company are recorded to address gaps to PMS RFP requirements. These BRM’s will be entered in JIRA and developed by the vendor company to meet Marriott requirements.

· Attended Discovery sessions and updated all the epics with notes, comments, screenshots and functional requirements based on the vendor demos of SHIJI PMS

· Participated in all MI HQ vendor discussion sessions (Integrations, deployment, security etc) as vendor point of contact, lead & document functional requirements, deep dive discussions and review sessions.

· Understand the PMS conversion and data migration such as migrate local interface to PMS system and work on PMS field mapping to ACRS (the source of truth) for all the PMS systems.

· Worked on different domains such as Admin Configuration, On Property Interface, Data Privacy, Cashiering, Groups Reservation, Reservation, Loyalty Program, Guest Profile. Front Office, Housekeeping and GXP Discovery (Empower App).

· Transport all the user stories to Microsoft excel and make updates periodically.

· Mapped the BRM’s requirements of the vendor companies to find discrepancies and document the differences on excel.

Environment: SDLC, Agile/Scrum, Waterfall Framework, MS Office, Microsoft Excel, JIRA, Visio, Confluence, SAFE Environment, Lightspeed PMS application. Legacy Systems upgrade and Integration with other downstream system

Part of CCMP (Care Coordination Modernization Portal ) – CCMP is a web-based application accessible 24 hours a day via FEPDirect. It serves as a central repository primarily for clinicians and analyst as a reporting tool that organizes and presents actionable data from multiple sources. CCMP project is a new application that would replace the CCP legacy application with improved accuracy of data, enabling seamless customer transitions between customer service and care management. It will provide a national unified cross-functional view of the member; be the Plan go-to reference for member health information, will eliminate reduces and improve operational efficiencies.

· Work with the Product owner to write feature level epics and user stories in JIRA.

· Worked on the Member Search, Member Medical Profile that includes Contract Information, Eligibility, Member and Contract Information, Claims Information, Medication list, Claims Search, Medication Search and Benefits inquiry, ID Card and Update contact Information features.

· Worked on Medical Claims that provides Claim information such as Date of Service, Diagnosis, Claim ID, Place of Service, Performing Provider, Procedure Code, Additional Diagnosis, Plan Code and Claim State. Worked on Claims Search to provide a user the flexibility to search the medical claims based on Diagnosis code, Diagnosis Description, Procedure code, Performing Provider name and NPI. The claim Id also links the user to view detailed information about their claim.

· Work with the solution architect to address each feature level requirements, dependencies and risk associated for implementation and come up with a plan to work with cross- team to identify and resolve the dependencies.

· Work with the data team to analyze the data dependences for each feature in the database and make enhancements required to include the data fields as per the requirements.

· Work with the product owner, UX and business stakeholders to identify requirements and write detailed level user stories.

· Analyze the required technical enablers by working with the architect and developers and write technical user stories and document them in the confluence page

· Analyze web services and include specific API”s for each feature documented in the user stories

· Conduct working sessions with the cross-team to have an in-depth understanding of the requirements and document them in the Sharepoint or Confluence page for reference

· Create Reference document that outlines higher level requirements with mocks for the CCMP application and document them in the Blue Web portal

· Document all the sprint work in the User Story Guide and Reference Guide

· Analyze the requirement gaps by testing functionality in the member360 (customer facing application) and CCP (legacy application) and documenting these gaps, discussing them and writing user stories based on the information.

· Demoing each sprint work to the Director’s office and internal team members

· Providing clarification and inputs to the developers and testers during the sprint regarding user stories and documenting all the edge cases into new user stories

· Feedback received during sprint review is researched and documented as new user stories as required.

· Participated in the Interview Process for hiring BA/BSA’s in the team

Environment: SDLC, Agile/Scrum, MS Office, Microsoft Excel JIRA, Postman, API, Visio, Confluence, SAFE Environment, Blue Web, CCP/Member360/CCMP application, Legacy Systems upgrade , SIT testing

Part of IT plan Team (Intake) – The IT plan team focuses on all the Intake projects. Based on the project’s requirements and other factors, the team understands what API’s should be provisioned or enhanced. The epics are written based on the project requirements and after the assessment of all the API’s required for a given project which the IT built team develops after planning

· Facilitate business requirement analysis and functional design work sessions including creating business presentations, communications, and documentation

· Analyze and understand the Solution Architect Diagram so as to document the API scope for a given project

· Create functional requirement and scope documentation using existing templates in JIRA

· Participates and collaborates with other teams to ensure successful PI planning sessions

· Collaborates with the cross-team members so as to understand or clarify requirements

· Document functional, integration, and testing requirements in epic

· Work with the IT Architecture & Development organization during development to address functional requirements and functional design clarifications

Environment: SDLC, Agile/Scrum, MS Office, JIRA, Swagger files, API, REST, Visio, Confluence, SAFE Environment, SIT Testing

Client: Anthem Insurance, Norfolk, VA

April 2017 – Jan 2020

Part of MADT Team (Mobile Application Development Team): Anthem Anywhere App and Sydney Health App

· Worked on the client/customer facing mobile application and make enhancements to the features that comes through different work efforts.

· Worked on the cross-functional teams to document the requirements for specified projects.

· Working in the agile/safe methodologies for the project.

· Analyzed existing data and identified gaps/data quality issues.

· Worked in large, complex data environments.

· Read the swagger files to understand the API's (REST) from SOA team that would be related to the functionality for the App.

· Participated in the PI planning that involves preparation for the body of work for the next 3 months for the team.

· Participated in the Test-ta-thon where testing is done for all the functionality of the application with different users in SIT and UAT environments. Defects were created and worked in subsequent iterations and resolved at the earliest.

· Created user stories for the Mobile team features which were shared with other teams such as RCP(Portal/Website), GBD (Medicare & Medicaid) to aid them in creating their user stories for the creation of Pharmacy Care Gap Project (Includes Integrated Pharmacy, Pharmacy Care Gap Notification, Medicine Cabinet,& Rx Benefits).

· Collaborated with the SOA teams to capture the API's required for different data elements.

· Collaborated with the SOA team to capture technical requirements and understand the feasibility of the functionalities desired by the Product Managers.

· Guide the UX team to create wireframes for the user stories for a specific project.

· Worked on adding different functionalities such as Action Items (these are products provided to the user to take actions such as reading health material subject or perform certain tasks as walking to accumulate points), chatbot (AI integrated to provide user specific answers) or device integration with fitbit, apple and samsung watches for the mobile application to track all the information provided to the user at one spot. This helps the brand to build up one stop shop for all the health-related user information.

· Analyzed adobe analytics to see the flow of traffic in the mobile application to understand the major functionality used by the users and make enhancements to the brand accordingly.

· Part of the Go-live Sydney app where the Sydney app was launched

Environment: SDLC, Agile/Scrum, MS Office, JIRA, Swagger files, API, REST, Visio, Confluence, SAFE Environment, Agile Craft, SIT testing

Client: Walgreens, Deerfield, IL

July 2016 – Mar 17

Position: Business System Analyst/Product Owner

Project 1: The RTH project was to develop Mobile applications to be used in the Walgreens Store: Operational Look Up, Manual Ordering, Store Receiving, Cycle Count, Goods Movement, Goods Return, Store To Store Transfer, Print Mylar’s/Signs & Picklist.

· Worked with the product, business and application teams to define and document functional requirements for a SOA/services/messaging team to build services.

· Analyzed existing data and identify gaps/data quality issues.

· Reviewed Business Process Document (BPD) given by the server team to understand the technical parameters for each features

· Primary responsibility for grooming several Content & API (RESTful) and involved in the Pre-grooming working sessions with the business and server team so as to create BRD's for each feature.

· Created User Architect Flow for each processes and discussed internally and sent to the UX team for the developments of the wireframes.

· Created functional, non-functional and technical user stories in JIRA

· Created Wireframe Annotation document which displays both the wireframes and requirements describing each flow and processes. This deliverable was used for the development of the functionality for each feature.

· Created Test Case Scenarios and tested the data send by the server team (SAP) in the Post Man Client validating all the outputs returned by the services.

· Created Requirement Traceability Matrix (RTM) for each Sprint showing the percentage of completed functionality.

· Created Demo Scripts and Story Board for the Demo and Tested the Mobile application prior to Demo and logged issues related to the functionality of the feature

· Presented weekly Demo to show the In-progress development of the feature application to the business and recorded walk through defects and co-ordinate with the developers and QA to resolve the defects.

· Presented the DEMO to the business and higher management team showing the progress of the UI development for each feature and documented the feedback by the business and incorporated all the changes in JIRA to track it.

· Used Vysor application to showcase the Operational Look Up and Manual Ordering application functionality for the feature.

· Used Camtasia Recorder 8 for the video recording of the Operational Look Up and Manual Ordering application.

· Had Refinement and sprint session with the team for every iteration.

· Demonstrated teamwork and ability to work with diversified multi-location team

· Worked in a shared services/enterprise level organization.

· Understand and document POS requirements to be integrated into the mobile application

· Environment: SDLC, Agile/Scrum, MS Office, JIRA, API, REST, Wireframe Annotation, Azure, Post Man Client, Visio, Google Drawing, Vysor, Camtasia Recorder 8

Client: Voya Financial, Windsor, CT

July 15- June 16

Position: Business System Analyst/Product Owner

Project 1: Enterprise Enrollment Program-

Project 2: Connect 2 Digital Solution, Retirement Customer & Sponsor Servicing- The project will develop new and enhance existing digital capabilities for customers while improving efficiency to back-end operations.

· Worked with Project managers to identify key Stakeholders.

· Assisted the project manager in estimates for new/upcoming features.

· Communicated team and project updates to management and client teams on a weekly basis.

· Performed GAP Analysis and assisted with analyzing problems and identifying applicable solutions.

· Created feature maps for the Enrollment Enterprise labeling the sub features for all the iteration.

· Created Data Mapping for different systems such as Agents, Home Office and Broker's application.

· Created Reports inventory explaining different kind of reports and their purpose such as Suitability Reports and EBI Reporting Tools.

· Performed Gap Analysis on the Disclosure texts and links for the EBI Tool and participant's view of the application.

· Documented current state and process map flow using Visio.

· Gathered and documented business and technical requirements from both formal and informal sessions while validating the needs to the stakeholders.

· Conducted interviews with end-users to collect requirements and business process information.

· Created Use Case Diagrams using Visio and presented them to the business and the development team as needed.

· Created user stories and mock ups in Version One

Environment: SDLC, Agile/Scrum, MS Office, PWeb, PSR Connect, Version One, Sponsor Web, Share point

Business Analyst – May 2011 to May 2015

Client: American Eagle Outfitters, San Francisco, CA

April 2014 – April 2015

Position: Business Analyst/Product Owner

Project description:

The project was to improve the current mobile web experience and the underlying technology to make a scale-able solution which meets the future needs. The scope of this project is to move away from the current “Branding Brand” mobile web experience and build a new mobile web site for the audience.

Analytics & Feedback (VOC)-Includes Test & Target, Opinion Lab Integration and Bazaar Voice (Product Ratings).

· Assists the Project team in developing business and system requirements deliverable using standard formats, including use cases, user stories, conceptual process models, flow diagrams and related documentation.

· Determine, document, and prioritize requirements from the business and present these requirements in a manner that is agreeable, measurable, and flexible.

· Analyze and documents business process and work flows for different systems such as POS which automates the transaction process and tracks sales data

· Conducted backlog grooming session, sprint and scrum meetings.

· Manage the organization and documentation of business requirements to ensure the Project Team develops and implements solutions that meet customer needs and minimize defects prior to implementation...

· Schedule, coordinate, and facilitate requirements gathering sessions with the business to identify and drive complete requirements.

· Assist in the development and update of project plans, schedules, and estimates.

· Work with project management to establish deadlines for completion of project deliverable.

· Document and update documentation for all internal system application and integration projects including user documentation and developer documentation.

·

Client: State Farm Insurance, Bloomington, IL

Jul 2012 – Mar 2014

Position: Business Analyst/Requirement Modeler

Project Description:

Project-1- The project was to provide enhanced client service by restructuring the web portal provided by the State Farm. Worked on the project to enhance the capability of ECS and automate the process so as to store all the updates and new information in the main database of ECS instead of all the individual applications.

Project 2

Integrated Customer Platform (ICP) is an effort to improve Customer experience while purchasing State Farm insurance for Auto/health/fire/life. It focuses on providing customers the ability to acquire and service all of their State Farm insurance and financial services products across all access points.

· Responsible to convert project specifications and statements of problems and procedures to detailed logical flow charts and document them in IT terms.

· Responsible for Requirement Gathering, Systems Analysis, and to perform JAD/ JAR sessions, maintain all the business and functional requirements under designated database using Clear case and create links between functional and business requirements.

· Responsible for making changes to the UI's and tracking/updating the UI's as per the business partners.

· Performed requirement analysis, went through all the use cases and issue logs.

· Worked on Commercial lines Property and Casualty Insurance including both policy and claim processing and reinsurance by using sequel queries.

· Participate in the preparation of UAT [User Acceptance Test] plans and their execution, and conduct meeting with the software testing team to assist in devising test plans, to test the robustness of the application at various stages of software development life cycle (SDLC) process.

· Maintained Requirements in the DOORs Database or the Share Point Repository.

· Worked and collaborated in other projects such as TAC, Claims-Mass Printing for ECS, Claims SAS Fraud Analysis, OCS DC4, Claims Document Viewer, HIS & ORG, Claims- Auto Estimating Vendor Upgrade, DVIP, Monitoring/Availability 24X7, ICD 9 and 10 and Automation of IL 919.

· Worked in creating deliverable for the Projects such as Transition Strategy, Knowledge Transfer Plan, Transition Support Plan, and Transition Acceptance Agreement.

Client: State of DE/Pro-Tech Company, Newark, DE

Oct 11 – April 2012

Position: Financial Business Analyst

Project Description:

The project enhances the Child Support system for the state of Delaware which is originally developed in Mainframes and DB2. The project involved getting the IV-D Interface cases and converting that into IV-A Cases in the DECSS Database system. The project in conjunction with ACS (Xerox Company) involved developing a new system called DECSS and implementation of the system for the State. This new system will consist of advanced technology and would be easier to access for the child support clients and the state.

Responsibilities:

· Gathered, analyzed, documented business and technical requirements and validated the needs of the business stakeholders

· Created Business Requirement Document (BRD), Functional Requirement Specification (FRS) document, User Requirement Specification (URS) and Change Request (CR) document for system application development.

· Worked with the SME's (Financial Analysts, Risk Managers, and Project Managers) and conducted joint requirements planning (JRP) sessions as a facilitator to gather requirements, define business critical needs and analyze the possible technical solutions.

· Performed analysis using sequel queries and documented the current behavior

· Elicited, analyzed, specified, and validated business needs of project stakeholders.

· Developed systems documentation and ensures updates conform to DHSS and ACS standards.

· Designed and modified test cases and scenarios.

· Co-ordinate various kinds of User Acceptance Testing (UAT) including regression testing, system testing, and integration testing and functional testing. A

· Involved in development of test cases and methods for unit testing, integration and functional testing, load and usability testing according to the application complexity and test requirements.