Description
Allow online as an option
Message clearly up-front that all requirements are required - your project fails if you miss any
Create a briefing meeting pre-piscine - offload the briefing / "Q&A about Piscine" to that session
Make sure it covers "100% requirements are required" on rubric
Make sure to emphasise and explain the CSS intention
Write up a specific list for this briefing so different people can cover the same material
Add a "make sure your whole group is set up on Slack" ticket before the first Saturday
Stop banning CSS - just tell them we don't give them any points for CSS
Maybe write up missing LOs from ITP as a reference list
Have people write down how they tested each rubric point, require at least one points at an automated test
Swap spaced repetition and shared bookmarks
Add a pointer about daylight savings
Look out for missing rubric depth in short demos
Maybe "if you skipped a rubric point, and had time left, that's bad"
Encourage (but don't require) having multiple demo assessors (and speccing how they coordinate)
Maybe try to record demos and see if it's useful
Rename to... TBD
"The Bridge"
"Project Based Assessment"
"Developer Skills Assessment"
You can’t perform that action at this time.
