1 / 8

IT Transition Team

IT Transition Team. Infrastructure Workgroup Meeting # 7 February 16, 2011 1pm-2pm. http://isites.harvard.edu/transition. Agenda . Feedback from the Sub-groups General Updates from Program Management Round 1: Infrastructure Customer Input/Feedback Review

hachi
Download Presentation

IT Transition Team

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. IT Transition Team Infrastructure Workgroup Meeting # 7 February 16, 2011 1pm-2pm http://isites.harvard.edu/transition

  2. Agenda • Feedback from the Sub-groups • General Updates from Program Management • Round 1: Infrastructure Customer Input/Feedback Review • Brainstorming session on the definition/input to the following on the Service Definition Template: • Tracking/Reporting Protocol • Dependencies/Pre-requisites

  3. Feedback from Subgroups • Feedback from the Sub-groups: How is the process going ? • Any issues for co-chair or Program Management resolution? • Any feedback from the Town Hall Meetings?

  4. General Updates from Program Mgt. • Foundational Group Updates: • Finance Group: on schedule to provide the Transition team with draft funding models/options this week; they will go through a piloting process to see if the models are usable • HR Group: Working on common job families and functions. Trimming down number of “unique” titles and streamlining sub-groups. • Communications Group: is behind on updating the isites; will be extending a part-time offer to a contractor to help; Jeff Lazarus will fill in the rest of the hours. New isites area called “All Staff Communications” – memos and important “informational” letters will be housed there. • Org Name Contest: Still coming – Transition team is behind on this • Organizational Structure still being worked on – meeting 2/17, then off-site • Some groups are starting to meet re: “cross-over” or “grey” areas: For Infrastructure we have two meetings setup: Security and Infrastructure Ops (w/client services); also looking at Video • Priorities for next couple weeks: Service Definition Templates and first round of Customer Input/Review

  5. Round 1 Customer Input/Review • Transition Team has updated the Infrastructure Round 1 Customer list to include the following: • Co-Chairs & PMs will reach out to these folks in the coming 2 weeks • Customers are being asked to identify “gaps” and ask clarifying questions • We’ll schedule in-person meetings to gain feedback • Customers will only review the Infrastructure catalog • Funding and organization are NOT being addressed in this review • This is the first review of more to come

  6. Brainstorm Exercise: Tracking/Reporting &Dependencies/Prerequisites • Let’s define some guidelines for what we mean by these Service Definition Template Fields: • Tracking/Reporting: What metrics will be used to manage/monitor service levels, customer satisfaction, issues resolution, etc., and what is the nature, frequency and audience for reporting? • Dependencies/Prerequisites: What are we assuming is in place to enable this service?

  7. Deliverables Reminder: INFRASTRUCTURE 24 weeks: Jan 1 – Jun 15 Key Activities Key Outputs WK1 1/3-7 WK21/10-14 WK31/18-21 WK41/24-28 WK51/31-2/4 WK62/7-2/11 WK72/14-18 WK82/22-25 WK92/28-3/4 WK103/7-11 WK113/14-18 WK123/21-25 WK133/28-4/1 WK144/4-8 WK154/11-15 WK164/18-22 WK174/25-29 WK185/2-6 WK195/9-13 WK205/16-20 WK215/23-27 WK225/31-6/3 WK236/6-10 WK246/13-17 • Service Catalog: Define Services • Define interim transition process • Develop 12 month implementation plan • New IT Service Catalog • Basic Interim Transition Process • 12-month Implementation Plan Service name, SL Plan Tracking, 80-100% complete Description, Customer Resp. Resources, by Mar-15 i Scope and Defined Pre-reqs/Depend. 2 week group review Customers Defined Defined, Identify Research Requests Get customer input / feedback Need to define the target service delivery model for each service category and each service. Then need to define how we get to the final delivery model, without breaking current (transition). Establish a 12 month implementation plan based on above – scope, schedule, resources, communications

  8. Questions? • Questions/Concerns??

More Related