Team Structure

Student teams and collaboration structure

  • There will be SIX teams based on the six trends detailed in the Horizon Report
  • Each team will consist of a Project Manager (PM) an Assistant Project Manager (APM) and 8 sub-groups based on the 8 norms of Net Gen (5-8 students in each)
  • Each sub-group will create a wiki page
  • Each team will create a TEAM wiki page with an overview and current technology sections completed by all.
  • The Project Manager and Assistant Project Manager will embed their finished multimedia on this wiki.
  • Each individual student will create a multimedia artifact and embed it on the sub-wiki page in the appropriate place.
  • Students will discuss using the discussion tab on their wiki (team wiki for overall group topics, sub-wiki for the sub-groups)

Project Manager Job Description

  • To take charge of primary editing of the TEAM wiki page that knits the 8 subgroups together for that trend/topic/team
  • To make sure that the subgroups contribute content to the each sub-wiki page as well as work on their own sub-page
  • To make sure that there are links to the other projects and to facilitate discussions/meetings/conversations within the group as well as give peer feedback to the other teams
  • To communicate regularly with the class teachers as to progress and discuss problems and issues as they arise
  • To create a personal multimedia artifact based on the team topic that may include some content from the subgroups for that team
  • To ensure all work is completed within the essential time frame
  • The Assistant Project Manager will support these objectives as well and fill in where the Project Manager is absent.
The first report is to be filled in by March 18th. Please fill in the PM and AM Report

Team Member Job Description

  • To collaborate with other member(s) to create a sub-wiki page for the given trend/topic
  • To complete a personal multimedia artifact based on the trend/topic and embed this in the wiki
  • To follow the given template and the assessment rubrics
  • To communicate, interact and complete essential work within the given time frame

Team Assignments

Students must register on the Google form and their teachers will be working to assign the students to groups. The link to the final Google Doc with group assignments will be posted here when complete. See the Project Structure Overview for an explanation of each of the teams, as shown below.


Team A - Mobiles

Main Team Wiki: Mobiles and NetGen Norms
A.1 Choice and Mobiles
A.2 Customization and Mobiles
A.3 Transparency and Mobiles
A.4 Integrity and Mobiles
A.5 Collaboration and Mobiles
A.6 Fun and Mobiles
A.7 Speed and Mobiles
A.8 Innovation and Mobiles

Team B - Cloud Computing

Main Team Wiki: Cloud Computing and NetGen Norms
B.1 Choice and Cloud Computing
B.2 Customization and Cloud Computing
B.3 Transparency and Cloud Computing
B.4 Integrity and Cloud Computing
B.5 Collaboration and Cloud Computing
B.6 Fun and Cloud Computing
B.7 Speed and Cloud Computing
B.8 Innovation and Cloud Computing

Team C - Geo-Everything

Main Team Wiki: Geo-everything and NetGen Norms
C.1 Choice and Geo
C.2 Customization and Geo
C.3 Transparency and Geo
C.4 Integrity and Geo
C.5 Collaboration and Geo
C.6 Fun and Geo
C.7 Speed and Geo
C.8 Innovation and Geo

Team D - The Personal Web

Main Team Wiki: The Personal Web and NetGen Norms
D.1 Choice and the Personal Web
D.2 Customization and the Personal Web
D.3 Transparency and the Personal Web
D.4 Integrity and the Personal Web
D.5 Collaboration and the Personal Web
D.6 Fun and the Personal Web
D.7 Speed and the Personal Web
D.8 Innovation and the Personal Web

Team E - Semantic-Aware Apps

Main Team Wiki: Semantic-Aware Apps and the NetGen Norms
E.1 Choice and Semantic-Aware Apps
E.2 Customization and Semantic-Aware Apps
E.3 Transparency and Semantic-Aware Apps
E.4 Integrity and Semantic-Aware Apps
E.5 Collaboration and Semantic-Aware Apps
E.6 Fun and Semantic-Aware Apps
E.7 Speed and Semantic-Aware Apps
E.8 Innovation and Semantic-Aware Apps

Team F - Smart Objects

Main Team Wiki: Smart Objects and NetGen Norms
F.1 Choice and Smart Objects
F.2 Customization and Smart Objects
F.3 Transparency and Smart Objects
F.4 Integrity and Smart Objects
F.5 Collaboration and Smart Objects
F.6 Fun and Smart Objects
F.7 Speed and Smart Objects
F.8 Innovation and Smart Objects

Project Structure Overview

Team Structure for this project will "mash up" Don Tapscott's book, Grown Up Digital, with the Horizon Report 2009 from the New Media Consortium and Educause to analyze the major emerging trends in education with the 8 Norms of NetGen Students.


So, the Horizon Report 2009 shows 6 major trends in College Education broken down by the time frame for full scale adoption. Additionally, Don Tapscott's work, Grown Up Digital, shows 8 norms of the NetGen generation. So, we will have six major project wikis in which the trend will be explained and discussed, but then the particular technology will be analyzed in terms of its ability to be used effectively as per each of the eight norms on eight sub wikis for each major group.

How are the teams structured?

The Horizon Trends are lettered A-F and the 8 NetGen Norms will be numbered 1-8. So, All of the A studentw will work on the A wiki for mobiles with a concise overview of its current and potential use in education, but the subgroups will review how the particularl technology can be adapted to meet their assigned Norm for the NetGen generation on a subwiki. See the grid below.


What will groups be doing?

Work on the project will evolve and move according to the following guidelines. Please review the Google calendar embedded on the project timeline on this wiki.