310 likes | 322 Views
TeamSpots All Over the Place. Implementation of a classroom collaboration tool in public and residential spaces. Surajit Bose Residential Computing Stanford University. Allan Chen Academic Computing Stanford University. GroupSpace. Supporting spaces and technologies for teams and groups.
E N D
TeamSpots All Over the Place Implementation of a classroom collaboration tool in public and residential spaces Surajit Bose Residential Computing Stanford University Allan Chen Academic Computing Stanford University
GroupSpace Supporting spaces and technologies for teams and groups Surajit Bose Residential Computing Stanford University Allan Chen Academic Computing Stanford University
Outline • GroupSpace Program • Traditional Methods of Collaboration • Benefits of TeamSpot • History & evolution of project • TeamSpot technology & features • New Paradigm for Collaboration • Locations • Technical and programmatic challenges • Internship program • Contact information
GroupSpace: The Program • Identify collaboration technologies and tools that have worked in the classroom • Provide those technologies and facilities in public and residential locations
GroupSpace Expectations • Why we did it • Increased use of team projects in classes • National trend towards collaborative spaces • Bring advanced technologies with proven needs outside the classroom • GroupSpace == Group Time
GroupSpace Components • Space and facility • Furniture • Whiteboard • Whiteboard capture • Presentation equipment • Large community display(s) • TeamSpot Collaboration Software
TeamSpot Collaboration Software • Most important component of GroupSpace • Suite of software tools • Features of note • Connect laptops to a group session • Take over a shared display • Transfer files between machines • New paradigm for collaboration
Traditional Methods of Collaboration • Huddled around a laptop
V1.1 V1.2 V? Traditional Methods of Collaboration • E-mailing documents
Traditional Methods of Collaboration • Meeting in spaces not designed for teams or collaboration • Computer lab tables • Coffee shops • Benches, etc
Traditional Methods of Collaboration • Combining various tools manually • IM • Email • Network space
So Why TeamSpot? • TeamSpot is a single solution • Speed and efficiency • Version control • As little or as much as you need
The Beginning: iWork • Interactive Workspace project • Graduate project in Computer Science • http://iwork.stanford.edu iRoom in use Simulation of iRoom
Production: SCIL • Stanford Center for Innovation in Learning • Wallenberg Hall
Evolution • Moving out of the classroom • Allow students to use their own laptops • Walk up, Connect, Get to Work • First “TeamSpace” installed Winter 2004 • Upgraded to TeamSpot software Winter 2005 • Reorganized as GroupSpace Winter 2006
TeamSpot • Major components: • Host computer • PointRight: pointer redirection to shared display • CrossWarp: transfer files
PointRight • Pointer redirection from your laptop to community screen Shared TeamSpot screen Your laptop
CrossWarp • Transfer documents, URLs, and other files from your laptop to community display via drag and drop • Also transfer between connected laptops
New Paradigm • Greater than sum of parts
GroupSpace Locations Library Core East Residences West Residences
Meyer Library • Main technology building • GroupSpace located on 24-hour lobby • Installed in Spring 2004
Meyer Library • V-shaped tables • 2 displays
Toyon Moose Room Residences – Toyon Hall • 200 sophomores • Moose Room • Installed Winter 2006
FroSoCo Computer Cluster Residences - FroSoCo • Freshman & Sophomore College • 200 residents • Computer cluster
Technical Problems • Definition of “ease of use” • Ease of use != Ease of administration • Laptop required for use • Stability and upgrades • Cables, power, networking • No keyboard & mouse • Lack of on-site, FTE support in residences
Programmatic Problems • Marketing • If we build it, will they come? • If they don’t come, what will we do? • Threshold to use • Training issues • Establishing space identity
Internship Program • Winter through Summer 2006 • 3 paid interns • 10 hours/week each intern • Learning, Design & Technology (LDT) program in School of Education
Internship Programs • Goals • Increase usage • Form relationships with courses & programs • Usage studies • Recommend programmatic and possibly technical changes
Ongoing Effort • Continuing to refine and evolve • Working with other schools What are you seeing?
Contact Us • Surajit Bose • surajit@rescomp.stanford.edu • Allan Chen • allan.chen@stanford.edu http://groupspace.stanford.edu groupspace@lists.stanford.edu