1. “ IT Governance” OC CIO Council 5/13/2010 Presented by: Carmella Cassetta
2.
3.
4.
5.
6.
7. Key IT Governance Decisions M.I.T. SLOAN CENTER FOR INFORMATION SYSTEMS RESEARCH IT Principles Decisions High-level statements about how IT is used in the business IT architecture decisions IT infrastructure decisions IT investment and prioritization Organizing logic for data, applications, and infrastructure captured in a set of policies, relationships, and technical choices to achieve desired business and technical standardization and integration Centrally coordinated, shared IT services that provide the foundation for the enterprise's IT capability Decisions about how much and where to invest in IT, including project approvals and justification techniques Business applications needs Specifying the business need for purchased or internally developed IT applications
8. Theoretical Process Framework for Building Strategic Business Alignment Vision Strategic Elements Business Process Architecture Application & Information Architecture Technology, Infrastructure & Organization Architecture Key Capabilities Operationalizing the Business Strategy IT Strategy Including Mission And Vision What we aspire to What will enable us to achieve the vision What is required to achieve strategies How work gets done What IT must provide How IT delivers Business Strategy
9. Governance – Iterative Process IT Initiative Request Approved Prioritized Initiative Initiative Portfolio Strategic Business Objectives Governance Application Portfolio IT Initiative Resource Schedule Scope Risk Key Business Capability Model
13. Key Capability Requirements Determine Our Business Capability Requirements to Achieve Our Corporate Strategy. We can’t optimize every function. This helps define our investment strategy. EXAMPLE
14.
15.
16. … And expands to include engagement & supporting processes
17.
18. 1 2 3 5 6 4 7 The Business submits an ITER to IT with VP approval IT Project Lead accesses ITER as Project or Small Enhancement Steering Committee reviews, approves, prioritizes ITER ITER is approved as a Small Enhancement (SE) SE is prioritized and moved In Stream ITER is approved as a Project for Scoping Project is scoped and a *ROM is created Project is re-scoped as a Small Enhancement (SE) and 2 nd page of ITER is completed EXAMPLE: IT Project Intake and Approval Flow “Phase 0” See p. 4 ITER is put into the Pipeline >160 hrs <160 hrs <160 hrs
19. 8 9 10 11a 12 11b 14 13 ROM is approved by CIO and Business VP A *CER is created If project is capitalizable or requires external consulting, new hardware, and/or new software > $50K < $50K Business Steering Committee ITSC Approved projects are prioritized and moved In Stream Project is Active From p. 3 IT Project Intake and Approval Flow “Phase 0”
20. EXAMPLE: IT Project Process Flow | 5 working days | | 5 working days | project plan | 5 working days | 5 working days The determination is made whether or not North America wants to a) engage IT and b) invest its limited capital on this proposed project The business secures conditional approval to move forward The project receives final approval or is re-evaluated
21.
22. Change Management Process Flow 1. The Business or IT initiates a project that requires a change to a CCi production environment 2. IT associate creates an online Production Migration Request 3. Testing is completed and approval signature is entered on the Production Migration Request form 4. The Business Owner (director or above) enters approval signature on the Production Migration Request form 8. IT Associate ensure migration is complete and updates status both on SharePoint and the Production Migration Request form 5. The IT Owner (director or above) enters approval signature on the Production Migration Request form Approved 6. IT associate ensures form is complete and all signatures are in place by 12pm PDT on Monday 7. The CCB reviews each migration request for approval