Thursday, April 08, 2004

Conference day 2 presentation notes: STAKEHOLDERS

Had quite a lively discussion about what a stakeholder definition mean?

Decided first had to talk about where they’d be involved in the process (what table will they be sitting at?)
[see diagram]
Information/instructional technology groups
library group
registrar
training units
users: students
users: faculty

CIC might like to consider:
-talking notes about integration of CMS systems with library systems, distribute to the provosts. Make sure it’s in executive summary form so that they’ll read it.
-Facilitating access to information on library systems/CMS integration. Series of screenshots, etc. A page where access to all CMS’s and a guest account for CIC schools are possible.
-More than a clearinghouse: not just a place where ideas are shared, but a power users work group. Get together on a regular basis.
-A statement from this workshop about the importance of collaboration to the CIO’s and the university administration. Best practices models.
-Ongoing support for prioritizing functional requirements for CMS implementation.

Add'l notes:
CIC "model way" to define who should be "at the table..." define tables
-maintaining autonomy in the CIC inst.
-CIC communication for more standardization among vendors
-coodinating many institutions can be a drawback for CIC licensing of courseware

CIC's role in RFP;s: clearinghouse for RFP's

Colalboration amongst CIC LT people RE: stakeholders
Capturing the process

CIC method for giving guest access to all of our systems 2 help get an idea. sharing help pages.

Who are stakeholders:
-faculty, students: in systems eval stages, tough to get back decent feedback. RFP processes: focus groups, functional requirements gathering: important to get feedback from large groups of constituencies. We need stakeholders to talk directly to developers and clearly define requirements

What is the eval period? when product is beta'ed for yr. after release?

Prioritizing requirements list/bugs list
Prioritizing the importance of stakeholders: pulling out specific people from these constituencies that can become the stakeholders.

Cross-pollination of knowledge between IT/Library.

Add'l stakeholders: IT/Inst. tech/Acad. Tech people.

Who is being represented in faculty representation? early adopters or people with a true feel for the systems?

Curriculum reform: is it a good pad to solicit from?

Who is your audience/ define populations: basic/advanced, etc.

Who sits at the table and what table is it?
-students at the assessment phase
-student affairs and other committees
-bringing university administration to the "decision who sits at the table" conference
-if administration can b aligned you can achieve efficiencies
-IT should look into overall University IT architecture
-Pople who are creating art "public service media"

Centralize vs. non-centralized knowledge repositories

Getting CIC to form administrative groups that can spread policy philosophies, buy in to the big issues.