Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reframe the full stack assessment around completing features #224

Closed
40thieves opened this issue Aug 3, 2023 · 3 comments
Closed

Reframe the full stack assessment around completing features #224

40thieves opened this issue Aug 3, 2023 · 3 comments
Assignees
Milestone

Comments

@40thieves
Copy link
Contributor

Which module(s) and week(s) does this change affect?
Module(s): Full stack assessment
Week(s): N/A

Why is this work important to do?

Completing the full stack assessment project is a requirement for trainees to join final projects.

In a recent Tech Ed Syllabus team meeting, @SallyMcGrath raised that the structure of the project is problematic and potentially working against the goals of final projects as a whole.

The general structure of the assessment is roughly to:

  1. Build the whole frontend
  2. Build the whole backend

This causes some issues:

  • Trainees are encouraged to spend a lot of time building a lot of "useless" stuff like headers/footers, and not focusing on the main functionality. This approach then bleeds over into the final projects
  • There's no thinking about the users or the "product", in other words, trainees aren't thinking about the problem that they are solving
  • Trainees don't prioritise completing a whole end-to-end feature, and instead build out only one half of several features

What is the work that needs to be done?

We should reframe the exercise to "slice" it so that trainees focus on completing end-to-end features, one at a time (presumably in a priority order).

Hopefully this shouldn't be too difficult, as the underlying content should be still be good, it just needs moving around.

Additional context

We would like to complete this before the next cohort gets to take the assessment (excepting LDN10, who are so close that we don't believe we can complete the work before they start).

Who might need to know about this change?

@CodeYourFuture/global-syllabus

@SallyMcGrath
Copy link
Member

We have a workshop that could happen during Node or Databases (it should be 2 hours though not 1) to support this

https://github.com/CodeYourFuture/CYF-Workshops/tree/main/breakdown

@SallyMcGrath SallyMcGrath added this to the Databases milestone Aug 6, 2023
@illicitonion illicitonion moved this from 📋 Backlog to 🔖 Ready in Curriculum Planning Dec 5, 2023
@illicitonion illicitonion moved this from 🔖 Ready to 🏗 In progress in Curriculum Planning Jan 16, 2024
@sztupy sztupy moved this from 🏗 In progress to 👀 In review in Curriculum Planning Jan 27, 2024
@sztupy
Copy link
Contributor

sztupy commented Jan 27, 2024

@Dedekind561
Copy link
Contributor

@Dedekind561 - to review in next sprint - 12/03/2024

@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Curriculum Planning Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

4 participants