...
...
...
...
11/12/2008 - Wednesday substitution for 11/11
1:00 pm, N42-286, CSS Managers
Agenda
- Update on the Exchange project (Deb Bowser)
- Deb Bowser posted her notes as presented to the group .
- High-Priority Item Roundtable, as time permits
Notes
- Oliver will be traveling and will not be able to attend this meeting
- Rob will be taking children to medical appointments and will not be able to attend this meeting.
- Kate is teaching all day and will not be able to attend.
- Mark will be working from home - plumber coming to restore hot water - but will have a Pubs Team member attend in his place.
...
11/7/2008 -- CSS All-Hands
12 am to 2 pm, Broad Auditorium, CSS All-Hands
Agenda
- 12:00 to 12:30 Lunch
- 12:30 to 01:30 Q & A, Town Meeting-style, mostly about the IS&T Organizational Assessment with Accenture.
- 1:30 to 2:00 Jerry will join us.
Notes
- Oliver will be traveling and will not be able to attend this meeting
- Jonathan will be traveling and not able to attend this meeting
...
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://mv.ezproxy.com.ezproxyberklee.flo.org - 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.
- 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.
- 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
...
11 am to noon, N42-286, CSS Managers
Agenda
- Quick look at the new CSS Managers wiki page (smyser)
- Quick recap: Hermes week one (othomas)
...
The All-hands agenda has turned into Lunch for the first 30 minutes (12-12:30), then 12:30 to 1:30 Q&A town meeting, then jerry joins us at 1:30.
Notes
- Jana works from home and cannot attend; access phone number is 781-436-3630.
...
11 am to noon, N42-286, CSS Managers
Agenda
- Ken Lloyd (klloyd@mit.edu) discussed the 1/2/3 prioritization of HR attentiveness to particular open position efforts.
- CSS All-Hands date and agenda setting. Nov 6 or 7, noon to 2; agenda is 1. lunch, 2. Q&A, mainly on Accenture project. Efforts will be made to ensure this is really all-hands.
- Future CSS_Managers' agendas -- will be assembled using contributions from us to a wiki-mediated agendas page that Rob will facilitate.
- Equipment -- be sensitive about sporting the very latest best stuff yourself, but if a staff person is using old, sad equipment, feel free to instill a point of pride by way of a new laptop, say.
- Accenture updates and discussion