Know every part you wrote deeply and the rest of the system broadly

In a team project, each member should be able to:

• Explain in depth the components they built: the logic, data flow, edge cases and why it was done that way.
• Explain in outline every other component: what it does, how it connects to theirs and who built it.
• Describe the whole architecture from the diagram without notes.

Individual marking is common. The University of Lahore's Islamabad campus guidelines, for example, assess each member on their own presentation and project work. A member who cannot explain the code attributed to them is in a weak position whatever the team built.

Before the defence, each member should walk the others through their code for 15 minutes. You learn the rest of the system, and they find the gaps in your explanation before the panel does.