FYP Team and Supervisor Checklist

Final year projects are rarely lost on technology. They are lost on people and time: a teammate who disappears for a month, a supervisor nobody meets until the mid evaluation, two members overwriting each other's code, or a team that discovers in the last week that nobody kept notes of what was agreed. Most of these problems are predictable, and most can be prevented with a few habits set up in the first two weeks.

This checklist walks through those habits in the order you need them. It starts with choosing teammates and agreeing expectations in writing, then choosing and working with a supervisor, running meetings and keeping notes. The middle chapters cover splitting work fairly and a simple Git workflow for a team. The last chapters cover keeping evidence of each member's contribution, what to do when a teammate stops contributing, and the checkpoints that keep the year on track.

Every item says what to do and how to check it is done. Rules on group size, supervision and evaluation differ between universities, so the examples from published guidelines, such as the University of Lahore's Islamabad campus FYP rules and the FAST School of Computing handbook, are there to show what rules typically look like. Git advice is checked against GitHub's own documentation and the Pro Git book.

The checklist works for teams in Pakistan, India, Bangladesh or anywhere else with a team capstone. Use it alongside the FYP Proposal Best Practices, FYP Report Best Practices and FYP Presentation and Defence Best Practices guides.