Team Exercise

A team exercise is one students hand in together: one participation, one submission and one result for the whole team. Four of the exercise types support it — programming, modeling, text and file upload.

Create a Team Exercise

Participation, in the Mode section of the creation form, takes Team instead of Individual. Team Size appears beside it and takes a Min and a Max; both are a recommendation that the dialog warns about but lets you override when you actually build the teams.

Making an exercise a team exercise

❗

Danger:

Participation cannot be changed once the exercise exists. An exercise that should have been a team exercise has to be created again.

Manage the Teams

Teams on the exercise's row in the course exercise list opens team management: every team with its tutor and its members, and the three things you can do to the set as a whole.

The exercise's teams

Create Teams by Hand

Create team opens a dialog asking for the team's Name, its Short Name and its Students, searched for by login or name. A Tutor can be given as well; a team without one is still a team, but the tutor is who Own teams filters the list down to.

The short name identifies the team across the course, so a team of the same people on another exercise reached through Import teams keeps it.

Edit and Delete Teams

Edit on a team reopens the same dialog on it, and Delete removes it along with whatever it handed in.

Editing a team

Export Teams

Export teams writes the exercise's teams to a file that another exercise can import.

Import Teams

Import teams takes teams either from such a file or straight from another exercise in the course. The dialog colors each source team by what it would collide with — nothing, a short name already in use, or a student who is already on another team here — and then asks for an Import strategy:

• Purge existing deletes every team in this exercise, and their participations with them, before importing.
• Create only imports the conflict-free teams and leaves everything already here alone.

Importing teams from another exercise

Collaboration

A team shares one editor: what one student writes, the others see. Text and modeling exercises both work this way, and the text editor also lists the team and marks who is in the exercise at that moment.

A team writing together

Team Overview

Team, on the exercise itself, opens the team's own page: who is on it, who its tutor is, and every exercise in the course the team takes part in with what it has handed in for each. Students, tutors and instructors all see the same page.

A team's page

What Students See

Students on a team exercise share one participation and one result, and write together in the live editor — see Exercises on the student pages.

Once the due date has passed, students can practice. See Practice Participations below and Practice mode on the student pages.

Practice Participations

Practice mode on a team exercise is individual: each student, with or without a team, starts their own practice participation, which belongs to the student and never to the team. It never changes the team's participation, submission or result, so the team's grading and scores stay as they are. Practice results are unrated and do not enter the course score.

ℹ️

Information:

A practice participation always starts from the exercise's starter code, never from the team's graded code, and text and modeling exercises have no shared editing in it. If you granted a team an extended deadline, its members can practice only once that extension is over.

• Participations on the exercise lists every practice participation as a separate row marked as practice, next to the team rows. A practice row shows the name and login of the student, not of a team, and the search finds it by either.
• The team's page does not list practice participations.
• For a programming exercise, tutors can read a student's practice repository. Editors and instructors can read and write it. See Repository Access.