Overview:

A well-structured team environment sets clear expectations and accountability systems from day one. This section describes what teams should know at the outset and how to maintain momentum and fairness throughout the project.

Why It's Important:

Structure helps teams stay focused, meet deadlines, and address issues before they become major problems.

What Teams Should Know on Day 1:

  • Project goals, deliverables, and timeline
  • Shared grading criteria
  • How conflict will be mediated
  • How communication will occur (Slack, Teams, email, shared docs, etc.)

Add "Team Signals of Trouble" to look for and address early:

  • One student performing 40%+ of the work
  • Teammates silent in meetings
  • Declining attendance
  • Avoidance of conflict
  • Late or missing micro-deliverables

Accountability Enhancers:

  • Weekly micro-deliverables with feedback, instead of one big deadline
  • Rotating roles: Facilitator, Recorder, Timekeeper, Devil's Advocate, Quality Controller. This creates interdependence and peer accountability to perform in these roles.
  • These roles are based on a group of 6 members but can be adjusted for a smaller group of 4 or 5 members by removing less important roles such as Timekeeper and Devil’s Advocate.