1. IT Services Transition Weekly Program Management Working Session February 22, 2011 | Tuesday | 11:30am – 1:00pm

2. Agenda Program-wide Status Snapshot: Key Updates Only (round robin) –Communications WG –HR WG –Finance WG –Steering Committee Org Planning Updates IT Service Delivery WGs –R1 Customer Input: Preliminary feedback and process for gathering and documenting feedback; updated timeline –Priorities for this week and next Preparation for Tomorrow’s TT Meeting 2

3. 3 Program-wide Status Snapshot: Key Updates Only Working Group Notes on Updates High-level StatusKey Issues / Open Items Finance (Laurie Gamble) Firmed up funding options and key criteria this week Began piloting a scenario service through the set of options just this morning None reported HR (Kelly Imberman) Continuing to work with Steering Committee to develop shared leadership competencies, specialized competencies, and related job descriptions CTO Search: assembled Search Committee; receiving and screening resumes, and preparing for Wave 1 interviews Next key milestone: funding strategy memo + accompanying packet of job descriptions Standing issue: Immediate hiring needs occurring in tandem with org design impacting speed with which jobs can be posted; major staffing challenges on WG Communications (Vaughn Waters) Standing-up comms infrastructure ~70% complete Launch for new iSite area for All-Staff Communications slightly delayed to this week WG hiring update Major staffing challenges on WG 3 weeks behind on FAQ refreshment; will be posted to iSite by COB today 3 weeks behind on new org name contest; adjusted workplan accordingly Steering Committee (Cathy Cho Yoo) ~20% complete with detailed org planning Beginning related governance piece Update from 2/17 org planning session None reported

4. 4 IT Service Delivery WGs 1.R1 Customer Input: Preliminary Feedback and Process Key feedback themes received to date? General progress of customer reviews? Process and timing for collecting, documenting, and gathering feedback 2.Priorities for this week and next Initial feedback from Steering Committee: cut through jargon; define plainly Research needs, process, timeline (Liz Egan) Resolve high priority design issues and ‘grey areas’ Update original Service Definition 1-pager Template (particularly around service level and performance metrics areas)

5. 5 REMINDER: Customer Input – Round I: Common Process and Key Dates Reminder: we are beginning our 1 st round of customer input with those customers recommended by your Working Group (WG) Co-chairs Round 1 will be approximately 1 week and run in tandem with the Steering Committee’s review Please note: additional rounds of customer input are being defined this week Process Overview Action ItemOwnerTimeframe Email list of people’s names and titles to Cathy, and review method WG PMs (in consultation w/ Co-chairs) By 2/7, M @ COB Consolidate and review with Steering Committee members C. Cho YooBy 2/8, Tu @12pm (by email) On 2/9, W @ 1pm (in-person) Finalize list and provide notification to all WG PMs, including standard invitation language to Round 1 Customer Input Reviewers C. Cho YooBy 2/10, Th @ COB Review communications with Co-chairs, finalize, and email out to Round 1 Reviewers WG Co-chairs + PMsBy 2/11, F @ COB Review respective list and definitions of servicesR1 Customer Input Reviewers 1 week: 2/11, F – 2/18, F (i.e., next week)  Submit comments to Co-chairs + PMs / Complete review sessions R1 Customer Input Reviewers By 2/18, F @ COB  Email feedback to Cathy, noting areas you’re incorporating vs. escalating for discussion WG PMsBy 3/1 Tu @ COB  Review + integrate comments and update Master Issues Log as needed; communicate w/ Steering Comm C. Cho Yoo2/22, M – 3/3 Th

6. 6 Preparation for Tomorrow’s TT Meeting Jointly prepare a status update together with your WG Co-chair(s) High-level snapshot on progress made to date (e.g., X total services identified; Y% of services flagged for further definition with other working groups) High-level summary of key issues WG is currently facing (e.g., top 2-3 design issues) Key feedback themes / patterns received from customers to date (e.g., no more than 1-2 key themes / patterns)