Pre-apprenticeship portfolios

[sofer]

• Learning outcomes need to be made more specific #787
• Portfolio reviews need to be set as homework earlier, probably at the end of Week 3
• Give clear instructions to use screenshots or code snippets from your own projects and to annotate each example
• Give time for learners to review each others’ portfolios in small groups, probably in Weeks 5, 8 and 11.
• Do a whole-class review first in Week 5, before sending them off into small groups, see General approach to code reviewing, mock interviews &c. #786
• Tutors will review each portfolio topic outside class time and give feedback through issues, probably before Weeks 6 and 9 and 12.
• The final portfolio reviews can happen at the end of Week 12.
• We need 2 tutors and can split the class up into 2 waiting rooms, while we meet one-on-one with each learner in turn.
• Portfolio reviews can be nothing more than an opportunity to listen to the learner: “Please screen share each of your portfolio pages in turn, displaying each learning outcome and drawing attention to anything notable. Be mindful that we only have about 20 mins to review all three portfolio pages".
• Take 1-2 minutes at the end for our feedback, including positive feedback and also reflection on any gaps or errors that we notice.