Conversation notes
==================
Any input based on all-hands?
- Trying to define CS seems to be the right thing to try to do
- What's the relationship of our CS list to other directorates' lists?
- What does "working as a department" mean for (IS&T) core services?
Very important we articulate the desired characteristics of a core service
Discussion of what kinds of things should be brought to the IS&T leaders
working group. Starter lists of similar things (see action items below).
- What characteristics are we currently using to claim something as
   core?
- What are the desired current characteristics in determining whether
   something should be core or not
- What is the community's view of our core services
Generic idea of core service
  - how we satisfy it now
  - examples of hows
- What core services are we not currently doing that we should be doing?
- What services should we sunset?
- Action: Brainstorm our (CSS) starter list of all IS&T services the way
   they are currently delivered (basically list of what we do)
- Action: Brainstorm our (CSS) starter list of characteristics we think
   should define an IS&T core service
- Action: Brainstorm our (CSS) starter list of characteristics that
   might currently define an IS&T service as core or not
- Action: Brainstorm our (CSS) starter list of IS&T core services that
   should be provided but are not currently services
Should we engage Marilyn in defining the process of communicating with
the MIT community and developing a process to refine core services with
the community?
This may be a long-term one-year project.
Needs to integrate with financials.
Anne: First drafts of zero-based budgets are basically due in three
weeks, which means the managers' parts need to be done in about two
weeks.
Given that, should we table the core services dicussion and perhaps even
the next CSS leaders meeting in favor of budgeting? Spend the next
meeting on a budget conversation and debrief.
"Services" and what we do are not the same. Example of mail services vs
specific execution of mail delivery.
Note: Ideally initial list will be the "what/how we do things today,"
but not too granular. And not so broad that we don't know what we're
talking about or don't agree on what they mean. Ideally, most of the
things in the list should roll up into higher-level service
descriptions.
The next step on this will be very mechanical. We will ask Pat to take
all the various lists of services we have (IS&T web site, services
spreadsheet, services list we brainstormed before, etc.) to create a
starter list of "things we currently do."
Oliver has volunteered to help coordinate this collection of lists with
Pat.
Anne's notes from the board
===========================
Agenda:
* Overview/Review
* Next Steps/today's agenda
* Wrap-up
* Next steps/next agenda (-> FY11 budget draft review)
   - List of "desired characteristics built in collaboration with other
     directorates
   - Complete current IS&T services list (Oliver, Pat?) from CSS
     perspective
   - Process suggestions
     + Internal CSS discussions/list completion - Next steps: roll up to
       core services or not
     + List of characteristics
     + Leverage IS&T leadership working group for cross-directorate
       agreement on service list (first); characteristics of "core"
* Roundtable
1. Actions (in parallel)
    a. Articulate value of current services
    b. Debate/hash out future characteristics of core services
2. What CSS "core services" should be...
      > Driven by
3. Incorporate into department core services?
===
5 Core Services (to date)
1. Provide IT Operating Environment
2. Provide Consultative Services
3. Easy to use interface for purchase and repair of hardware
4. Athena managed computing environment
5. Provide cost-effective SW solutions
===
Parking lot:
* Have core services "sponsors" in the community?
* Doc combining "core" list with the "hows" and beginnings of
   characteristics
* How to add "new" and sunset other services
Lists of different kinds of things
* Current services (what we're doing now)
* What core services should be
* Desirable future characteristics of core services
* What about Terry's statement? Does it include any core services?
* CSS Leaders core services list
   - Does not include material from other 3 lists
   - No external input
   - Getting more general as we go on
Service = "what" we do or an umbrella with the "whats" listed below?
Oliver's notes on the list of lists
===================================
Current Services (what we do today) and their characteristics:
        - penetration
        - impact of going away
        - perceived value to MIT of having such a service
        - perceived value of current service implementation to MIT
        - importance of client(s)
        - investment in service
        Our internal assessment of these factors have all been implicitly
        driving the discussion whether we've put things into core or not.
Our personal assessments of what Core Services for the central IT
organization at MIT should be:
        - Email and calendaring
        - Network
        - Desktop deployment and management
        - ...
Characteristics of current services that might make them core:
     - scale/adoption
     - can they be provided elsewhere
     - ... (we made this list already)
Desired characteristics of a core service
        - fully resourced to be sustainable
        - fully resourced for effective support and operations
        - redundant
        - secure
        - efficient
        - easy to use
        - centrally agreed as high value to community
        - driven by centrally defined and agreed upon policies
        - effectively maps against key use cases and personas
        - externally sponsored
        - externally governed
        - ...
       
Current core services
        - Do we have any core services that meet all of our desired
       characteristics? Probably not. What are the deltas?
Future core services
      - What core services should we have but do not currently?

  • No labels