11 am to noon, N42-286, CSS Managers 

Agenda

  • Review software vocabulary for Software Grid (jmhunt & atticus) 
    • printed writeup of proposed vocabulary was circulated by Jon at the meeting.  That text is posted off the main CSS wiki page.
    • we reminded ourselves of the IS&T new web site look-and-feel, into which this download page would fit. 
      See http://cspace.mit.edu
    • Questions that came up:
      • Should we devote web page space to the "Support" column on the web page (the group says Yes) 
      • How do we indicate that a product is on the way out?  How do we convey the current lifecycle discussion about why we're at the version we're at and you should know about it.  (Maybe Hermes.)
      • What about the "More details..." link -- put all the useful detailed info there.  Include the product lifecycle info, accessibility compliance, download size, etc.
      • How do we decide to provide, say, Brio, instead of some competitor tool -- who is "we" and "when did they know it?"  Sidebar conversation about the internal team-driven politics of major software acquisition.
      • How does a product get on to the web page -- what set of checkboxes in a checklist will get the product into which category?  Mark Kate and other in-CSS support providers want to have a more formal process and have a role in shaping the check list.  Jon went through attempts at this years ago, but it's time to do it again, and better.
      • What's the timeline for having this finished up -- Spring 2009, in sync with the IS&T web site. 
    • There seems still to be a tug-and-pull about the purpose of the download page in a use-case sense.  Have we tried from a customer view to articulate scenarios about why they come to the page and what they ought to find there.  It was done a while back, but for a very and more complicatted different page design.   
    • People need to be able to see the design intent of the original redesign project so that we know what the plans were so we can align with the features articulated.
  • Call for cost-cutting/cost-saving measures (tjm & all).
    • Taemin call Tim to get a list of cost-cutting measures that CSS plans to undertake, to provide content for an Academic Council meeting .  Are we being asked to look for ways to save MIT money from the CSS perspective?  Yes. 
      What measures might we take and wouuld they save money...  If you have ideas, forward them.  Rob will create a page to receive ideas.  That page will be off the CSS wiki page. 
  • Proposal for a 30-minute agenda item in a future meeting -- how to link when a product is decided upon to the process of creating training and documentation and product front doors and so on.  Each is different, but what is the visible triggering event for the create-support-for-this process.  Where in the organization are these facts articulated?  Agreed on as a topic for a future meeting.
  • Proposal for a 30-minute review of the IS&T web site design with respect to the information architecutre.

Notes

  • Wilson is traveling
  • Oliver will be traveling and will not be able to attend this meeting
  • No labels