...
11 am, N42-286, CSS Managers
Agenda
- Response to Discusssion of Jerry's letter forestalling an announcement of organizational review results at an All-Hands.
- unfortunate external events interlocking with Terry Stone's intention to shape or reshape her area.
- EVP attention to IS&T is new for us. Facilities, HR, etc. having been larger targets at the time, it's our turn now. Terry's background is from the financial services world, a very technology savvy sector, where IT = Business. Terry "gets" that MIT is a special place, and her scrutiny is a positive thing. Steady as she goes, as far as CSS is concerned. But be cognizant of the larger movements. There is no "date" for Terry to deliver on her effort. Remember that the original IS&T review was of the VP-staff dynamic. This is still the overall focus.
- Review of changes to the Products & Services list
- Should we keep a lot of "subservices" under a broader service name. The "service owner" in Wilson's view has the budgetary responsibility for making it happen. The real point person should be the Group or Team that is responsible for the service. So, the template is "DCAD. Contact Jeff Reed". Preference for combining as more subservices.
- This document was not public before. If elements of this are more public via Christine Cavanna and the RMs then what is put on it needs to be edited so they don't get inappropriate first contacts.
- Another concern is how many different kinds of services there are. There is a service for every 1.65 person. The preference in the past was to acknowledge all the little subpieces. Mark remarks that we have too many places where we try to say similar things. Another purpose of this list is "if it breaks, who do I talk to?"
- Are these the right list of products and services? how do we define a service -- can we measure it? Staffing, budget? Can customers "sign up" for it? Is it "Email" or is it "mail delivery, spam filtering, accounts listing, etc." The customers idea is one filter on what to have on the list.
- Must we commit to coming up with cost and price listings for services we say we own. Or are services really owned by someone else and we do an activity _on behalf_ of services that are really owned elsewhere, maybe even outside IS&T.
- ACTION: we now have a modified list of these, with some additions, etc. We have updated the current document correctly. Wilson leans in the direction of simplifying the detail.
- Discussion focussing on the decision making process for doing a Software Release Project (e.g. FileMaker 10)
- invited Deb Bowser to attend
- Overview of Software Release Process
- Issue Management & Reporting - New guidelines for reporting on client issues, outages, events etc.
...