FYP Team and Supervisor Checklist

What this checklist is

A step-by-step checklist for the people side of a final year project. It covers choosing teammates and a supervisor, a written team agreement, meeting cadence and notes, splitting work fairly, a Git workflow the whole team follows, keeping evidence of each member's contribution, handling a teammate who does not contribute and the checkpoints that keep the year on schedule.

It has 8 chapters and 34 checks, each with how to verify it and how much it matters. For final year and capstone project teams.

Chapter by chapter

1. Pick teammates and agree expectations (4 checks)

Your teammates matter more than your idea. Choose people you can rely on for a full year, check the group rules and write down how you will work together.

2. Choose and work with a supervisor (4 checks)

A supervisor who knows the area and meets you regularly is one of the strongest predictors of a smooth year. Choose deliberately and agree how you will work.

3. Meeting cadence and notes (4 checks)

Regular meetings with written notes keep the team aligned, give the supervisor visibility and create a record you will need later.

4. Split work fairly (4 checks)

Fair work splits prevent resentment and make individual marking straightforward. Give each member clear ownership, track tasks visibly and share both code and writing.

5. Git workflow for a team (6 checks)

A shared repository with a simple branch and pull request workflow prevents lost work, makes review normal and records who built what.

6. Keep evidence of contribution (3 checks)

If marks are individual or a dispute arises, you need records of who did what. Build them as you go, not after a problem appears.

7. Handle a teammate who does not contribute (4 checks)

A teammate who stops contributing is one of the most common FYP problems. Act early, stick to facts, involve the supervisor and protect the project.

8. Timeline checkpoints (5 checks)

Fixed checkpoints across the year stop work from bunching at the end. Put your department's dates in the calendar and check the team against each one.

How it works on Sefism

The checklist is one page: each check has a severity (must, should or nice to have) and a concrete way to verify it, and members can tick checks off as they go. Every chapter is open to everyone.

Every claim is checked against the sources listed on the page (7 cited).