You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Build the whole frontend
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
The text was updated successfully, but these errors were encountered:
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:
This causes some issues:
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
The text was updated successfully, but these errors were encountered: