Overview

Throughout the semester, your team will complete 3 team projects:

• Project: Open Source Contribution with Superset
• Assignment: Group Architecture Document
• Presentation: Group Architecture Presentation

This assignment has two graded parts, each with its own deadline:

Part	Weight	Deadline
Team Formation	1%	Graded during your tutorial in the Week of September 14th
Team Agreement	1%	Due in your tutorial in the Week of September 21st

Team Formation (1%)

Team formation is graded during your tutorial in the Week of September 14th.

You must spend your best effort to form a team of 4 in your tutorial. You are not allowed to have team members from another tutorial.

To get full credit, by your tutorial in the Week of September 14th your team must have:

• Formed a team of 4 (or the size your TA approves if the tutorial does not divide evenly).
• Chosen a team name.
• Created a private Slack channel that includes every team member and your tutorial TA.
• Introduced yourselves to each other.

Your TA will check these items during the tutorial. If you have not found a team by then, tell your TA during the tutorial and they will place you in one.

Team Agreement (1%)

Your signed team agreement is due in your tutorial in the Week of September 21st.

Your team agreement is a binding document between your team, in case a conflict arises. The team agreement governs the contribution factor for each group activity. The contribution factor may be between 0%-110%.

Your team agreement must cover how the contribution factor is affected in the following situations.

• When a team member is unreachable or unresponsive (please specify the response times clearly)
• When a team member misses a scheduled meeting
• When a team member drops out
• When a team member is unable to complete their part of the activity
• When a team member's contribution violates the academic integrity policy (see the section below)

Your team agreement can also optionally contain other situations in which the contribution factor is affected. This is up to the discretion of the team.

To get full credit, your team agreement must be signed by all team members and submitted before your tutorial in the Week of September 21st.

Academic Integrity in Team Work

The Academic Integrity section of the syllabus applies to every piece of group work in this course. Working in a team does not dilute your individual responsibility. You are fully responsible for every commit, document section, and slide you contribute. The University's Code of Behaviour on Academic Matters applies to each member individually.

Common ways teams get into trouble:

• Copying from another team, a previous offering of this course, or a solution found online, then submitting it as the team's work.
• Sharing your team's code, documents, or slides with another team. You may discuss ideas and clarify requirements with other teams, but you must not exchange work products.
• Submitting generative AI output as your own work. The syllabus requires your work products to be original and not copied from generative AI tools. Ask the course staff before using such tools for a piece of coursework if you are unsure.
• Adding a teammate's name to work they did not contribute to, or letting a teammate commit under your name. Every contribution must be attributable to the person who actually did it.
• Knowingly including a teammate's copied work in a submission. If you suspect a teammate's contribution is not original, do not merge or submit it. Raise it with the teammate first, and with your TA if it is not resolved.

What your team agreement must say about academic integrity

Your team agreement must include a short academic integrity section that covers, at minimum:

1. A commitment from every member that the work they contribute is their own and complies with the syllabus policy.
2. How the team reviews contributions before submission (for example, every pull request is reviewed by at least one other member, and the reviewer asks where unfamiliar code came from).
3. What happens to the contribution factor of a member whose contribution is found to violate the policy. The team decides this number, but it must be stated explicitly.
4. An acknowledgement that the team agreement cannot shield anyone. If the course staff find that a submission contains plagiarized or otherwise improper work, the University's process applies to the responsible member regardless of what the team agreement says. The contribution factor adjustment in your agreement only governs the team's internal split of the grade.

Teams that are transparent early are treated far better than teams that hide a problem. If you discover an integrity issue inside your team, tell your TA as soon as possible.

Arbitration with TA

Although rare, sometimes, team members are not able to work with each other due to various reasons. At any time, if any member feels like the team agreement should be enforced, they should set up a private meeting with the TA to discuss the matter.

Please raise this issue only as a last resort.

The TA will use the team agreement to make a final decision on the contribution factor for each team member. The TA will not apply adjustments that are out of the scope of the team agreement, and also will not enforce team agreements that are overly vague.

If you are unsatisfied with the result, please ask the TA to reach out to the course instructors for a final decision.

Submission

There is nothing to upload for team formation. Your TA records it during your tutorial in the Week of September 14th.

For the team agreement, write it in the Google Doc shared with your team by your TA. All team members must sign it before your tutorial in the Week of September 21st. Your TA will check the signed document during that tutorial.