Project teams

What it is

Small teams building something real. The goal is not a perfect product — it is the experience of working with other people towards something that still exists when you close the laptop.

A project needs more than a programmer

This is the single biggest reason the community is not limited to people who write code. A project that only has engineers on it usually produces something that works and that nobody can use.

• Someone who writes the code
• Someone who designs how it looks and behaves
• Someone who understands the data or the AI part, if there is one
• Someone who keeps the documentation honest
• Someone thinking about who it is for
• Someone keeping the team organised

How teams form

Usually at the weekly meeting. Someone describes what they want to build, other people say what they could contribute, and a team either forms or it does not. An idea that nobody volunteers for is telling you something useful.

Agree responsibilities on day one

Before any work starts, write down who is doing what and roughly by when. Most student projects do not collapse for technical reasons. They collapse because three people each assumed somebody else was doing the part nobody did.

If you cannot deliver your part, say so early. That is normal, and it is only a problem when it is discovered late.

Finishing

Demo day is the natural deadline: a fixed date, an audience, and something to show. Projects that never have a deadline tend never to have an ending either.