1. Project Initiatives Identified by the CIA Project
Chuck Hill
(Developed using the METS 2018 Discovery Work PPT)

2. Table of Contents Table of Contents: Slide Discovery Overview 3
Objective of Discovery 4
Assumptions of Discovery 5
Benefits of Discovery 6
Overview of Discovery Outcomes 7
Discovery Analysis Process 8
Discovery Expected Timeline 9
Recommended Initiatives by CIA Project Team
10-11
Recommendations of Discovery Initiatives by Project 12
11/11/2018

3. Discovery Overview
The “CIA Project Discovery” project represents the tasks and initiatives that were identified by the CIA Project Team and Business Representatives from HCEO, SMRT, MNSure, and the County to be considered as pre-requisites to the Curam Instance Alignment project implementation.
The advantage of formalizing the discovery work into a project will allow us to account for resource capacity, formal tracking, reporting, and visibility provided within the standard project process.
The CIA project work will continue in those areas not impacted by these tasks  
11/11/2018

4. Discovery Project Objective
The objective of the discovery effort is to provide more detailed information and analysis, including identifying causes of pain points for business, identifying possible solutions or options, and providing recommendations to the ISDS and METS PMT groups.
The CIA Project Team and Business Representatives met and identified tasks and initiatives to be considered prior to, as a part of or after the implementation of the CIA Project
The team prioritized these items and a recommended prioritized was presented to both the ISDS and METS PMT groups
Project Sponsors for this Discovery effort have been identified and include Lisa Koenig, Deb Tibstra, Jeff Jorgenson and Rachel Petersen
11/11/2018

5. Assumptions of Discovery
Discovery initiatives will include those that impact all Cúram projects and not just the CIA project
ISDS and METS PMT will approve the priority of all the initiatives and the discovery team will work in priority order
Discovery efforts will be staffed accordingly with representation from:
DHS Business (ie HCEO, SMRT, MNSure, & County)
Business Architects
Business Analysts METS & ISDS
Technical Architects & Developers
Quality Assurance
Given Discovery is a formal project – teams will provide the necessary resources and commitment to keep the discovery within scheduled timelines
Discovery efforts will be contained through the approved scope; discovery should not be viewed as a full blown design phase within a project
11/11/2018

6. Benefits of Discovery Benefits include:
Ensure accurate identification of the problem and its causes
Provides critical information to assist in business planning, system planning, and development
Allows for identifying solutions that are holistic and include process improvements, communication improvements, using existing functionality, identify existing defects to be corrected prior to merge, and building new functionality
Allows for optimal horizontal integration of different systems and business processes
Allows for stream lining of business processes
11/11/2018

7. Overview of Discovery Outcomes
Possible Outcomes for Discovery Effort:
Identify root cause of pain points
Determine high-level requirements
Provide recommendations for solution options
Provide analysis on resource needs and level of effort
Identify any additional linkages to the item or items that can be worked on as a package/project
Provide Executive Summary and Detail Analysis documentation
11/11/2018

8. Discovery Analysis Process
11/11/2018

9. Discovery Expected Timeline
Intake
Discovery Analysis Process
Frontend Process:
Business Request: Provides first pass at stating the business need (from business’ POV). It is MN.IT’s responsibility to use the Business Request as a foundation for further elicitation.
Business Case:
MN.IT engages with business to assess business strategy and evaluate perspective on business. The Business Case will include clearly documented information derived from sources such as a work request, management direction research or analysis. Goal: provide a well-supported, data-based explanation of the business need.
Preliminary requirements:
If the analysis conducted during work on the Business Case suggests a technical solution is needed, preliminary requirements will be documented. Goal: ensure solution developers and system/business architects have enough information to identify and compare solution/application options, and the ability to support intended capabilities. This includes evaluating perspective on technology environments and collaboration with systems architects, and developing proof of concept.
Solution Options: The Solution Options provides an overview of solution options. Each will be compared to the requirements identified in the previous step, and each will be accompanied by information related to its costs/benefits. Goal: illustrate options for PMT and business representatives so they can quickly assess their choices in terms of costs, benefits and feasibility.
Solution Recommendation: Provides MN.ITs solution recommendation (based upon extent to which requirements are met, costs/benefits, etc.) Goal: ensure business understands costs, risks and benefits of the recommended solution and is positioned to make an informed decision about how they would like to move forward. The Solution Recommendation is the final deliverable.
Analysis Presentation:
BA and PM provide overview of analysis/findings to PMT and business decision makers, and presents solution options and solution recommendation. BA or Dev presents (depends on project, etc.)
1-2 Weeks
10 Weeks
11/11/2018

10. Recommended Initiatives for the CIA Discovery Effort
Person-Centered Delivery:
Includes the policy, issues, roadblocks with business processes, technical analysis, gap identification, impacts of gaps, and identifies business requirements and changes to business processes due to sharing and maintaining of information by multiple programs.
The discovery will impact decisions about:
Data sharing across program areas: Includes the policy, access rules and changes to business processes for sharing and maintaining data across multiple program areas.
Single Integrated Case (vs. current approach of 2 separate IC’s for SMRT and METS): Includes the approach, solution & overall of additional programs coming on to one instance of Curam (SMRT/METS and future programs)
Evidence / Evidence Brokering: Includes how Evidence is used and how the maintenance of evidence can impact the case structure.
Automation of Blackout Periods: Includes the elimination of the manual workaround of ‘holding changes’ and taking into consideration the period from the interaction with the Federal Hub through the notice generation process.
Effective Dates: Includes the incorporation of effective date processing for future date changes, and the actual date evidence changes.
11/11/2018

11. Recommended Initiatives for the CIA Discovery Effort
Participant Identification Management:
Includes the ability to merge participant records (SMRT into METS), the processing changes for Prospect persons and data clean-up to improve participant matching
Security, Organization, and Location Structure:
Includes understanding of each worker in METS and SMRT with county involvement to confirm dual users and duplicate users with security groups, security roles, and Org/Loc structure, and identify valid and consistent methods to collect contact information for each user ; would also include User Identification Management for the merging of duplicate users
Training, Communications and Support:
Includes the establishment of roles and ownership, and the coordination of training and support across programs
Reporting Communication:
Includes providing technical support, communication, and identifying table changes for units developing reports and queries on Curam-based tables.
11/11/2018

12. Recommendations for Discovery Initiatives by Project
11/11/2018