96 roy

ALN Conference New York, NY: 

ALN Conference New York, NY Faculty Development and Cross-Unit Collaboration: The Roles of Academic Colleges & Information Systems Lucinda Roy and David Taylor, Virginia Tech “US” “THEM” (What awaits for those who don’t collaborate)

Faculty Development Institute: Background and Inception : 

Faculty Development Institute: Background and Inception 1992: Budget Cuts, Low Morale Collaboration between Provost and V.P. for Information Systems Investment in Faculty Funding: Re-allocation of Resources Instructional Development Initiative: Focus on Instruction

Instructional Development Initiative: 

Instructional Development Initiative Structure Faculty development Student support: computer labs, training, PID’s Curriculum development and Facilities upgrades Focus: core courses with large enrollments

Evolution of FDI: 

Evolution of FDI 1993 Pilot: 50 faculty 1994 - 1996: 1025 faculty Early: Know your computer, general purpose software, multimedia Recent: Classroom presentations and Web course development; projects

FDI: Structure: 

FDI: Structure Workshops Computer Software Network connection (Ethernet)

Keys to Success:Planning, Assessment, Support: 

Keys to Success: Planning, Assessment, Support Faculty driven Ongoing assessment: feedback before, during and after Continuing support: Year-round specialty workshops Consulting, project management, grant-writing Resources: server space, hard/software New Media Center CEUT grants

Academic Colleges:Guardians of the Curriculum: 

Academic Colleges: Guardians of the Curriculum The curriculum is the life-blood of an institution. It is not just what we teach, it is the who, the how, the when, the where, and the why of what we do. It makes fundamental assumptions about learning and teaching. If we tack on technology to a traditional curricular architecture, our faculty development initiatives will fail.

Cross-Unit Collaboration:Why It’s Essential: 

Cross-Unit Collaboration: Why It’s Essential Successful transformation relies upon genuine cross-unit collaborations (C.U.C.s) rather than cosmetic ones. It involves a re-visioning of roles. Faculty development initiatives should be jointly coordinated by depts., deans, Provosts, VPs for Inf. Systems. This can only work when tied to an explicit reward system (e.g.computer, support)

Approaches at Virginia Tech: 

Approaches at Virginia Tech Faculty development linked to the curriculum and project-oriented. Team (60+) of faculty and staff who share a dissemination role in Cyberschool. Teacher/Techie combo. Dual and joint funding tracks. Problem-solving, active-learning approaches. (ACCESS)

Lessons Learned : 

Lessons Learned Less PR, more substantive data gathering Attack reward system early. Apply methodologies to other contexts, new learners, new projects. (LLS, ‘A’-TECH, Service-Learning, Project CI) Indulge frequently in conversation across units and across the curriculum. Ask the hard questions in assessment.

Lessons Learned II: 

Lessons Learned II Joint faculty appointments. Select good teachers. Take an holistic approach to faculty development and it will gather its own momentum. Anticipate burn-out; anticipate initial extensive support, then encourage and reward peer support.

Slide12: 

http://www.cyber.vt.edu/ACCESS