Fairly early on in this MOOC we had to form teams. I’m very interested in how this process works because it seems quite different than how we typically assign groups in the classroom. Note that I used the term “assign”.

Below is detailed information on the assignment, team formation and suggestions for teams. Are you using any of these during your team or group work? Do you provide the groups/teams with detailed information? Can the kids self -select? Are the students coached on selecting teams based on interest and complementary skills and knowledge?

The Following information was taken from the Designing a New Learning Environment, Professor Paul Kim, Stanford University

• There is no deadline to form a Team, but it is an important step to complete so that you can begin meeting, working, and innovating together!
• Anyone may create a team. When you create a team you are the Team Leader.
• The Team Leader can add new members by contacting classmates and asking them for their registered email addresses.
• When creating a Team, use detailed descriptions and information so that others will be able to thoughtfully consider whether your Project idea and interests may be a good match.
• If you have started a Team and are looking for members, you should use the Students menu (under Community) to find recruit your classmates.
• If you are looking for a Team to join, you should use Teams menu (under Community) to search for different teams. Use the contact button on the team page to contact all Team Members the Team Leader to join the team. Every time somebody invites you to their Team, you will receive a new invitation under your Conversations, Team notifications tab. That message contains links to accept or reject an invitation.

• Team formation has a very open dynamic, at any point you can decide to leave a Team and join a new one, without penality. The Team Leader can decide to remove inactive or uncooperative members from the Team. (In that case the member will receive a team notification about this decision, and if you think that the Team Leader has made a mistake, you can appeal Team Leader’s decision. If half of Team Members agree with you; you will be added back as a member of the Team. If a Team Leader chooses to leave his/her Team, he/she can assign Team Leadership to another user. Continuity among Team Members will be important to successful execution of the Team Project, however all users have the option to switch a Team that is not a good fit for them.

• The recommended Team size is 4-7 people.

• You may only be a member of one Team at a time.

• One of most important variables in Team composition is shared passion about the project idea / topic area. We suggest that Teams be made up of people with a range of backgrounds and technical skills, but ultimately a shared interest in the idea is what will support project momentum and involvement. It is useful to think about geographical considerations in a variety of ways: if you are considering an educational innovation for primary education in Tanzania, for example, it would be very useful to have a team member from, or knowledgeable Tanzania, to help inform analysis of needs, barriers, implementation, and sustainability. However, geographical considerations, such as time difference, may also come to play when collaborating or scheduling Team Member tasks. We encourage you to think and be transparent about these in terms of what is important for your project and for your working style, while also demonstrating the flexibility and generosity of spirit that will help us grow from each other’s perspectives and experiences.

Getting Started with Your Team:

• Start communicating about your Team Project idea. Complete and maintain your Team Profile with an up-to-date (brief) Project Description (these may start simply as general interests, and may change or evolve over time).

• Every Team has a Team Journal. You should feel free to write on it about your Team activities, post pictures of your meetings or collaboration strategies, and write about your new ideas or progress for the Team Project. The Journal can also be used as a discussion tool. Your classmates will be able to follow your team blog and receive updates.

Team Project:

• Teams will design a new educational technology or learning environment catering to 21st century environments and learners. Designs should include interaction activities and learning support features in ways that are effective and appropriate for today’s computing and communication devices, and that consider the classroom, school, and community ecosystem in which it will operate.

• Presentation of your design should include details about the users, environment, and educational objectives of your design (the “who? what? when? where? why? and how?” questions).

• Your presentation should also address how your designed innovation would implemented and sustained, including considerations about idiosyncrasies with various learning devices (e.g., web, iOS, mobile devices, and Mac/PC) and infrastructure requirements (e.g., cellular network, wi-fi, Bluetooth).

• Your team should create and defend a business model (non-profit, for-profit, or hybrid) for the launch and scale up their solution.

• You will not need to conduct an actual needs analysis or develop an actually functioning technology or solution. You may describe a hypothetical solution in detail through text, visual mock-ups, and prototypes.

• Additional consideration will be given to teams that come up with system feature ideas presenting meaningful learning interaction and performance analytics.

Evaluation:

• The Final Team Project will undergo the official Peer Review process.

• The Final Team Project is due at 11:59pm (Pacific Standards Time) on Sunday, December 16.

• The broad criteria for Final Team Project Evaluation (these will be addressed further later in the course):

1) Creativity and originality of the system design (Is the design substantially distinguishable from existing and conventional solutions?);
2) Educationally sound (Does the design promote higher order learning or generate learnable moments?);
3) Engagement and interactivity (Is the design engaging and interactive for the learner?);
4) Accessibility (Is the design accessible for people with disabilities or for people living in underserved communities?)
5) Scalability and sustainability (How sound is the implementation plan and business model?)

• At the end of the course, you will also be evaluated by your other Team Members on your contribution to the Team efforts and Team Project. In addition to your Assignments, this peer evaluation will affect your Rank in the course.

Intellectual Property and Confidentiality Considerations:

• Some of the major goals of this course are to instill the mindset for thinking about innovations aimed at improving education, and to create a space for developing those ideas into thoughtful designs. We would like you to continue to develop your work and Projects beyond this course into the real world. The Intellectual Property rights relating to your Individual Assignments, Team Assignments, Journal entries, and other materials created by you remain with you (and with the Co-Creators for Team Assignments and Jointly Authored Works)–they are not Stanford’s, not Venture Lab’s, and not Dr. Paul Kim’s.

• At the same time, this space is public to others in the course–all Journal and Forum posts, as well as all Assignments will be visible to all others enrolled in the course. Viewing and learning from each other’s discussions and work products will expose us to new ways of approaching different problems and will help us develop a more critical eye for the benefits and limitations of technology solutions. Because all projects are shared with other DNLE-ers (strictly for educational purposes), an idea or product requiring strict confidentiality or formal business agreements would not be a good candidate for a Final Team Project. Please consider this when creating or joining a team.