1 / 10

Oregon Benefits Online

The Oregon Benefits Online (OBO) Scope Identification workgroup conducted a thorough analysis of the Oracle system built for OBO, evaluating its alignment with the Master Scope document. The results highlighted significant mismatches, indicating that the system does not meet business needs without extensive customization. Usability, the user interface, content accuracy, and overall functionality were key areas of concern. The workgroup recommends halting current project activities, providing a detailed project roadmap, identifying future business requirements, and exploring other systems that may better serve the needs.

solomon-chapman
Télécharger la présentation

Oregon Benefits Online

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Oregon Benefits Online Scope to System Comparison 1

  2. What We Did • The Oregon Benefits Online (OBO) Scope Identification work group conducted a high level analysis of the Oracle system built for OBO using the Master Scope document. • Compared each line of the Master Scope document to the demonstrated system to evaluate alignment. • The comparison was focused on the needs of the business. • The comparison was completed and findings were determined based on demonstrations of the OBO system. • Completed the analysis ahead of schedule. 2

  3. What We Did Not Do • Hands-on testing. • Any technical analysis of the underlying foundation. • Prioritize any scope items beyond the already identified Future Phases section. 3

  4. Categories • Usability – The general intuitiveness, workflow, navigation and ease of data entry. • User Interface – The look and feel of the OBO system. • Verbiage/Content – Displays accurate information, wording, phrasing and correct placement. • Functionality – Does what it is supposed to do in order to meet the business need. 4

  5. Findings • Our analysis concluded the OBO system did not meet the Master Scope and it appears extensive customization would need to occur. • Issuing benefits timely will be at risk due to the communication inconsistencies within the Customer Portal. • Workload and accuracy will be negatively impacted due to the usability deficiencies within the OBO system. • Extensive staff training and business process re-engineering would have to occur to use the “out of the box” OBO system. 5

  6. Findings 6

  7. Findings 7

  8. Findings 8

  9. Proposals • The Scope to System Comparison Workgroup recommends that DHS should not implement the OBO system as is. • Additionally: • Stop all project activity • Create a thorough project roadmap • Determine future needs of the business • Gather requirements • Research systems that would meet the needs • Once these are done – reinitialize the project • The recommendation is to not spend the time and money to do a time estimate for OBO system completion because of lack of agreed upon requirements. 9

  10. D i s c u s s i o n 10

More Related