WIP: Specialism final projects

[adamblanchard]

The idea here is to:

1. Document how the final projects will/can run
2. Capture the learning goals for all final projects
3. Capture the specific requirements for each specialism

Note: I think the specialism specific requirements should live in the specific course, but for now just keeping them together while we review them.

I have written these requirements from a mix of staff conversations, the old final project repo, and the new learning goals overviews. They are 100% up for discussion, I am only writing these down as a starting point.

I would already like some feedback on what's in here. Initially from the staff team, and later from the wider mentor group.

The easiest way to view it:

1. Final project readme
2. Frontend course requirements
3. Backend course requirements

[saloumeh-67]

Based on our talk at HYF 2.0, Here the bullet points for the final P (from Soheib and me) regarding the project presentations.

Please feel free to suggest changes if needed, and add your ideas! 🙃

🎮 Final Project Presentation Guidelines
When: 3rd week of the Foundation project
Duration: 7–10 minutes per team

Presentation structure:

Start with your Trello board → Explain your workflow, task organization, and process.

Show your project → Demonstrate the working game/application.

Talk about contributions → Each team member should briefly explain what they worked on.

Requirements before presentation day:
✅ Project must be fully deployed and live.(did we decide which platform for deployment?)
✅ Prepare a QR code linking to your live project.

During the session:

Share the QR code so other teams can test your game on their devices.

[saloumeh-67]

I think it would also be good to have consistent steps for the Specialization final project.
That way, trainees would know what to expect in advance, and we don’t have to wait until two days before the presentation to tell them.

Would you like me to draft a similar set of guidelines for the Specialization phase as well?