The Junior Phase Final Project is a summative assessment offered to students at the tail-end of Jr Phase. Students must complete a fullstack CRUD application using the NERD stack over the course of several days. Students are asked to submit a recorded video walkthrough of their application, along with a link to the app's repo itself.
The JPFP is considered a substantial part of the "Senior Gateway", and students must demonstrate sufficient proficiency with our stack to move forward in the program. As such, grading these projects swiftly is of paramount importance to a good student experience and the operational health of the program.
-
Students will submit a 5-10 video walkthrough of their application by Sunday 6pm, the day it is due. They will link the video on the readme of their application.
-
Fellows are responsible for an initial triaging of their Learning Team's projects and mark each student as At Risk (<= Tier 3 passed), or LIKELY PASS (Tier 4 and up). They should aim to complete triaging their Learning Team within 1.5 business daya of video submission (Tuesday Lunch). Instructors should come up with a plan that accounts for fellows on Help Desk assignments during this time, and may assist in facilitating the triaging.
-
Fellows may use the submission videos as well as the ldcli tool to speed-up triaging
-
If on deeper viewing, Fellows decide a submission is At Risk they should overcommunicate that to the team, so Instructors may grade it more thoroughly.
-
Grades are weighted as the following:
- 70% Requirements
- 30% Rubric Score
Both the Requirements and Rubric documents are located in the JPFP Project Repo.
-
Superfellows are responsible for grading their cohort's At Risk JPFPs.
-
Jr Phase Fellows are responsible for grading their cohort's Likely Pass JPFPs
-
In the event there is a large batch of JPFPs to triage, Superfellows, Instructors should communicate and work with PMs/ Directors to delegate grading work to the rest of the instructional team.
-
The team should strive to complete grading the Requirements (no rubric score or feedback) for ALL students by Week 6 Wednesday at 6pm.
-
The team should complete grading the Rubrics for all students by Friday EoD
-
-
Once all assignments are graded, Instructors may give Fellows the go-ahead to DM members of their Learning Team their individual pass/fail status (around Thursday EoD).
-
Instructors and Fellows should coordinate on when to release full grades, ideally by early Async Week (Monday or Tuesday)
-
Grading projects should take ~30 mins for Likely Pass submissions and ~60 mins for At Risk (leveraging the video overviews and ldcli). Do not feel the need to dive down the grading rabbit-hole for each project.
-
Instructors do not need to provide written feedback for projects. Students are invited to request feedback over an Office Hour during Async Week.
-
Any partially-completed requirements should receive a score of 0.5 on the Requirements list. Broken code that requires some massaging to get it partially/fully working should receive 0 credit.
-
It is okay (and encouraged) to prioritize a quick grading turnaround over absolute thoroughness. The primary goal is to ascertain the pass/replay status of students as quickly as possible.