How many students should be in a group project team?

The short answer: three to five

For most university group projects, teams of three to five work best. Below three, a single dropout can sink the project. Above five, coordination cost climbs, someone can hide, and the work rarely divides cleanly enough to keep everyone busy.

The right number inside that range depends on the project. Bigger deliverables with clearly separable parts can carry five; a tight, fast-moving brief is usually better at three or four.

Why bigger teams get worse, not better

Adding people adds communication links faster than it adds hands. A team of four has six pairs to keep in sync; a team of six has fifteen. That overhead is exactly where free-riding and missed handoffs creep in, because it gets easier for one person's absence to go unnoticed.

Match the size to the assessment

Before you fix a number, look at what you are asking teams to produce. If the deliverable cannot keep five people meaningfully busy, five is too many, and you are designing in a passenger. Size the team to the work, not the other way around.

Keep sizes even across the cohort

Uneven teams create a fairness problem: a group of three doing the same brief as a group of five is not being marked on equal footing. When you form teams, aim to keep sizes consistent, and decide in advance how you will handle the remainder when the cohort does not divide evenly.