Creating an Enterprise Project with Agencies


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Creating an Enterprise Project with Agencies

  1. 1. Creating an Enterprise Project with Agencies Presentation for the Mental Health Transformation Workshop State of Connecticut Department of Information Technology January 25, 2007 Steven C. Casey, Director of Business Development for Health, Human Service and Education
  2. 2. Establish a Mission and a Vision <ul><li>Total Commitment by Participating Agencies </li></ul><ul><ul><li>Build business case </li></ul></ul><ul><ul><li>Present business case </li></ul></ul><ul><ul><li>Identify critical success factors, risks, and mitigating strategies </li></ul></ul><ul><ul><li>Develop implementation plan </li></ul></ul>Steve Casey, DOIT 2
  3. 3. Governance with Statutory Authority – Makes decisions and sets priorities <ul><ul><li>Governing Board / Steering Committee </li></ul></ul><ul><ul><li>Business / Program Committee </li></ul></ul><ul><ul><li>Finance Committee </li></ul></ul><ul><ul><li>Technical Committee </li></ul></ul><ul><ul><li>Security Committee </li></ul></ul>Steve Casey, DOIT 3
  4. 4. Funding <ul><li>Bonds </li></ul><ul><li>Surplus </li></ul><ul><li>Grants </li></ul><ul><li>General Fund </li></ul>Steve Casey, DOIT 4
  5. 5. Current Models <ul><ul><li>CJIS - CT Justice Information System </li></ul></ul><ul><ul><li>Core-CT - HR and Finance </li></ul></ul><ul><ul><li>CEN - CT Education Network </li></ul></ul><ul><ul><li>GIS - Geospatial Information System </li></ul></ul>Steve Casey, DOIT 5
  6. 6. Project Management <ul><li>“ Rome wasn’t built in a day” </li></ul><ul><li>DOT can’t build a bridge overnight </li></ul><ul><li>Nobody can build a system “tomorrow” </li></ul>Steve Casey, DOIT 6
  7. 7. Project Management (cont.) <ul><ul><li>Establishes Best Practices </li></ul></ul><ul><ul><ul><li>Milestones with Timeline </li></ul></ul></ul><ul><ul><ul><li>Disciplined Process Management </li></ul></ul></ul><ul><ul><li>Reduces Risk of </li></ul></ul><ul><ul><ul><li>Not achieving goals and </li></ul></ul></ul><ul><ul><ul><li>Complete failure </li></ul></ul></ul>Steve Casey, DOIT 7
  8. 8. System Development Life Cycle (SDLC) <ul><li>Problem Definition </li></ul><ul><ul><li>Roles and Responsibilities – </li></ul></ul><ul><ul><ul><li>Executive Sponsor </li></ul></ul></ul><ul><ul><ul><li>Business Manager </li></ul></ul></ul><ul><ul><ul><li>Project Manager </li></ul></ul></ul><ul><ul><ul><li>Business Staff </li></ul></ul></ul><ul><ul><ul><li>Technology Staff </li></ul></ul></ul>Steve Casey, DOIT 8
  9. 9. SDLC – Problem Definition Project Manager (PM) <ul><li>The PM should be a resource paid for (by the grant, bonding or general fund). </li></ul><ul><li>The PM should write first the high level project plan in order to develop the resources and cost estimate for this initiative. </li></ul><ul><li>This plan should be presented to the sponsor and rest of the workgroup. </li></ul><ul><ul><li>All of the resources (Hardware/Software, Staff, licenses, hosting, maintenance) that are needed to complete and maintain this project should be specified. </li></ul></ul><ul><li>IF INTERNAL RESOURCES CAN NOT BE OBTAINED TO FULFILL THE PROJECT PLAN THEN THE FUNDING HAS TO PAY FOR THE EXTERNAL RESOURCES TO COMPLETE THE PROJECT. </li></ul><ul><li>The PM should make sure there is consensus on the plan and get final signoffs from all stakeholders (Commissioners, Business and Program leaders of all agencies) </li></ul><ul><li>PM should call the necessary meetings with the stakeholders, keep and distribute minutes. </li></ul><ul><li>The PM should be the single Point of Contact to DOIT. </li></ul><ul><li>The PM must ensure that the solution is Enterprise-Wide Technical Architecture (EWTA) approved. </li></ul>Steve Casey, DOIT 9
  10. 10. SDLC <ul><li>Business Requirements </li></ul><ul><ul><li>Identify Agencies and Divisions (Federal, State, and Local/ Public and Private Non-Profit) </li></ul></ul><ul><ul><li>Identify Systems </li></ul></ul><ul><ul><ul><li>ADT - Admission, Discharge, Transfer </li></ul></ul></ul><ul><ul><ul><li>EMR - Electronic Medical Records </li></ul></ul></ul><ul><ul><ul><li>Pharmacy </li></ul></ul></ul><ul><ul><li>Reporting Capability </li></ul></ul><ul><ul><li>Research Capability </li></ul></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>HIPAA </li></ul></ul><ul><ul><li>Disaster Backup and Recovery (DBAR) </li></ul></ul>Steve Casey, DOIT 10
  11. 11. SDLC - System Design Using Enterprise Information Architecture <ul><ul><li>Infrastructure Requirements </li></ul></ul><ul><ul><ul><li>Program Language and Database </li></ul></ul></ul><ul><ul><ul><li>Common Data Dictionary </li></ul></ul></ul><ul><ul><ul><li>Data Standards (XML - messaging) </li></ul></ul></ul><ul><ul><ul><li>Standard Data Fields </li></ul></ul></ul><ul><ul><ul><li>Data Warehouse (ETL) </li></ul></ul></ul><ul><ul><ul><ul><li>Extract </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Transform </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Load </li></ul></ul></ul></ul>Steve Casey, DOIT 11
  12. 12. SDLC <ul><li>System Construction </li></ul><ul><li>Testing </li></ul><ul><li>Implementation </li></ul><ul><li>Post–Implementation Audit </li></ul><ul><li>Production Maintenance </li></ul>Steve Casey, DOIT 12
  13. 13. <ul><ul><li>RFP or Master Agreement contract for Project Development Team </li></ul></ul><ul><ul><li>RFP for Design, Construction, and Implementation </li></ul></ul><ul><ul><li>Evaluation </li></ul></ul><ul><ul><li>Contract Award </li></ul></ul><ul><ul><li>Attorney General review of contract and </li></ul></ul><ul><ul><li>Contract Approval </li></ul></ul>Procurement – Ethics and Competition Steve Casey, DOIT 13
  14. 14. Proper IT project execution will save time, $ and ensure quality results System Development Methodology Roles & Responsibilities: Define Problem Define Business Specs Design System Construct System Testing Implemen- tation Post Imple- mentation Audit Realization of Benefits Customer Defines IT Participates IT Manages Cust. Participates IT & Customer Co-manage Cust. Manages IT Participates Initial Cost/Benefit Assessment & Go/No Go (here & at each arrow) Result: Mutual Understanding at a Detailed Level of What Needs to Be Done Cost/Benefit is Reconfirmed IT Owns This Process and Is Responsible For Overall Execution Steve Casey, DOIT 14
  15. 15. Project or Program Steering Committee TECHNOLOGY TEAM BUSINESS PARTNERS <ul><li>Team members shown are examples. Each Wheel will be unique, depending on the initiative or phase needs. </li></ul>Successful projects have active participation from both the business and technology staff throughout a project. Business Manager Business Requirements Lead Development Lead Infrastructure - Production Support Lead Security Lead Executive Sponsor Business Representatives from other Impacted Lines of Business Design Lead Support/Consulting Roles : Finance Lead Enterprise Architect Facilitator Deployment Lead Test Lead Technology Manager An IT Project Roles Wheel: Test Lead Steve Casey, DOIT 15