SharePoint Implementation Case

Cluster CollaborationAn Argument for Microsoft SharePoint

Rebecca Adams

Allison Nakonek

Robert Elmore

Zane Stark

Case Build Implement Conclude

The Problem

• Blackboard, ISMS• Platform interconnectivity• Resource relevance• Usability and Functionality

• What its worth• Ohio Business Top 50• Cluster Primary driver of recognition for

the College


The Solution

• Academia meets Business• Gantt charts, customizable

lists, sub-sites, permissions• Deep Integration

• Fully compatible with Microsoft Office productivity suite

• Usability• Familiar Microsoft layout

• Quality Collaboration Tools• Wiki’s, Blogs, Versioning


• Four Main Sites– Courses website

• Sub-sites for each course– Team Collaboration – Client Collaboration– Faculty Administration

• Increased functionality for users• Advanced search criteria• Special permissions• Customized layout to fit Ohio University

The Build


• Main Courses– Course Announcements– Calendar– Links to each specific site

• Specific Sites– Announcements– Calendar– Links

Course Site


• Team members only• Wiki and Discussion for enhanced collaboration• Calendar and Tasks for time management

– Ability to view standard calendar and Gantt

Team Collaboration


• Similar to Team Collaboration– Client and Teams has access

• Shared Documents– Clients post documents– Students post prototypes

• Links on homepage for relevant web pages– Could post student Y drive URL

CollaborationClient


• Forum for only faculty discussion• Shared Documents

– Course Docs (i.e. Syllabi) posted for Cluster Director

• Calendar – Collaborate on exams dates

FacultyAdministration


• Initial Investment• Risk Reduction• Cost Savings

Cost-Benefit Analysis

Hard Cost Benefits Soft Cost Benefits

Tangible Intangible


• Transparency• Training Processes

– Super users– Professors– Students

• Maintenance• User concerns

Implementation

SharePoint Implementation Case

Education

Transcript of SharePoint Implementation Case