Action items from last Checkpoint retro

common-content/en/module/checkpoint/assessing-demos/index.md

@@ -13,16 +13,7 @@ We give feedback after every demo, including a run-down of each rubric point. Th
 
 Where possible, we suggest having two assessors in a demo session, to get more opinions and discuss any uncertainty.
 
-These are typically our trainees' first demos. We expect significant improvement through the course. The first sprint is expected not to be good (but sometimes is!).
-
-<dl class="c-rubric">
-  <dt>Clearly introduce the topic of the demo.</dt><dd>Someone watching should be able to state the topic of the demo in one sentence. This topic should match how the trainee introduced their demo. If a trainee said their demo was about writing clear code, but it was actually about how to debug a test failure, they missed this.<br /><br />The topic <strong>must not</strong> be "I will tell you about my project". It must be more specific than a project overview.</dd>
-  <dt>Explain what was done</dt><dd>Someone watching should be able to state what you have done in one sentence.</dd>
-  <dt>Explain the reasoning behind a choice.</dt><dd>Someone watching should be able to explain why you did at least one thing a particular way (and why it was a better choice than alternatives).</dd>
-  <dt>Show relevant code or artifacts (e.g. a website, a ticket, an discussion).</dt><dd>Someone watching should be able to identify at least one artifact of your work.</dd>
-  <dt>Stick to your time limit.</dt><dd>You should know how long you have for your demo, and stick to that time. You will be given a warning when you're running low on time. If a trainee is not done speaking at the time limit, they missed this. Finishing early is fine.</dd>
-  <dt>(Stretch goal): Ask questions.</dt><dd>Someone watching can state at least one question that was asked of the audience that is not "any questions?". The point of this is to engage the audience and get them thinking/caring about the demo. The question should generally be rhetorical - you don't have time to wait for answers.</dd>
-</dl>
+You can see the rubric on [the Demo block of each Checkpoint day-plan](../sprints/1/day-plan/#demo).
 
 To run a demo:
 * Make sure someone is keeping time. They should clearly indicate when the trainee has 30 seconds left, and when they hit their time limit.

common-content/en/module/checkpoint/assessment/index.md

@@ -9,7 +9,7 @@ time=15
 
 The fourth class day will be interview day. Your interview will take place in a hiring platform, [Evidenced](https://www.evidenced.app/). An assessor will ask you questions about your code and your projects. You can be asked about any part of any of your projects, so make sure you understand it all, including the parts your teammates wrote.
 
-The success criteria is listed on the end of sprint review page. Read it carefully so you know what you need to do to succeed.
+You can see the details of the interview in [the day-plan](../day-plan/).
 
 ### Prerequisites:
 

common-content/en/module/checkpoint/demo/index.md

@@ -21,7 +21,7 @@ At {{<our-name>}} we expect you to demo your work to the class. You must have ma
 
 You will demo something about your project work this sprint to the group.
 
-You will have 2 minutes to explain what you did and why. Your demo will be assessed according to the rubric below.
+You will have 2 minutes to explain what you did and why. You must use at least 90 seconds of these 2 minutes. Your demo will be assessed according to the rubric below.
 
 Make sure you are comfortable with the tools you use to present your work. If you are giving a demo in-person you will connect your laptop to a screen/projector and present to the room. If you are giving a demo online you will share your screen on the call.
 
@@ -51,11 +51,11 @@ The person running the session (either a member of staff or a volunteer) will as
 
 These are some criteria we will be using to assess your demo. You must meet 5 of the 6 criteria, and if you skip one we recommend you skip asking a question. This is not an ordered list - you can complete these criteria in any order.
 <dl class="c-rubric">
-  <dt>Clearly introduce the topic of the demo.</dt><dd>Someone watching should be able to state the topic of the demo in one sentence. This topic should match how the trainee introduced their demo.<br /><br />The topic <strong>must not</strong> be "I will tell you about my project". It must be more specific than a project overview.</dd>
+  <dt>Clearly introduce the topic of the demo.</dt><dd>Someone watching should be able to state the topic of the demo in one sentence. This topic should match how the trainee introduced their demo.<br /><br />If a trainee said their demo was about writing clear code, but it was actually about how to debug a test failure, they missed this.<br /><br />The topic <strong>must not</strong> be "I will tell you about my project". It must be more specific than a project overview.</dd>
   <dt>Explain what was done</dt><dd>Someone watching should be able to state what you have done in one sentence.</dd>
   <dt>Explain the reasoning behind a choice.</dt><dd>Someone watching should be able to explain why you did at least one thing a particular way (and why it was a better choice than alternatives).</dd>
   <dt>Show relevant code or artifacts (e.g. a website, a ticket, an discussion).</dt><dd>Someone watching should be able to identify at least one artifact of your work. Slides don't count as an artifact.</dd>
-  <dt>Stick to your time limit.</dt><dd>You should know how long you have for your demo, and stick to that time. You will be given a warning when you're running low on time.</dd>
+  <dt>Stick to your time limit.</dt><dd>Your demo must be 90-120 seconds long. You will be given a warning at 90 seconds. If a trainee finished before 90 seconds, they missed this point.<br /><br />If a trainee is not done speaking at the time limit, they missed this rubric point, and anything they said afterwards will not be counted towards the rubric.</dd>
   <dt>(Stretch goal): Ask questions.</dt><dd>Someone watching can state at least one question that was asked of the audience that is not "any questions?". The point of this is to engage the audience and get them thinking/caring about the demo. The question should generally be rhetorical - you don't have time to wait for answers.</dd>
 </dl>
 

common-content/en/module/checkpoint/interviews/index.md

@@ -1,11 +1,11 @@
 +++
 title="Interviews"
-time=45
-objectives = [
-  "Predict and explain the execution of a computer program",
-  "Reason about where and when software is executed",
-  "Refactor and iterate code based on new requirements",
-  "Extract simple composable functions for common use cases"
+time=15
+tasks = [
+  "Introduce yourself.",
+  "Explain why you want to do the Software Development Course.",
+  "Explain what you have built.",
+  "Demonstrate your understanding of code you have produced.",
 ]
 [build]
   render = 'never'
@@ -15,29 +15,59 @@ objectives = [
 
 You will be asked to join a video call for your technical interview. We use an interview platform called Evidenced.
 
+You will be given a time-slot and link before Saturday. We expect you to be available from 10am until 5pm, even though you should only be needed for 15 minutes.
+
 ## What to expect
 
-- The interview will be 15 minutes long
-- You will be asked to discuss a feature from a project you have worked on during the Checkpoint.
-- You may have written this feature yourself, or it may have been written by someone else in your group.
+- The interview will be 15 minutes long. It may end slightly quicker, or go on slightly longer - you don't need to worry about timings, your interviewer will make sure you fit everything in.
+- Your interview will be online. You can come into a class space to do your interview on your laptop if you prefer, or can do it from home - whatever works better for you.
+- You will be asked to discuss features and code from the projects you have worked on during the Checkpoint. We will only ask you about the three projects you did in this Checkpoint. We will not, e.g., ask about your TV Show Project.
+- You may have written this feature yourself, or it may have been written by someone else in your group. You are expected to be able to talk about them all.
 - You will be asked to share your screen. You must be able to share your screen within 60 seconds of being asked. You will have an opportunity to practice using the interview platform before the interview day.
 - You should be ready to share your screen and talk about any of your projects. We recommend you have all of your projects open in VS Code and a web browser before starting the interview, so you can easily switch to one.
+- You are not expected to write new code in this interview. We may ask you things like "There's a bug here, talk about how you would fix it" or "If we wanted this project to have an extra feature or work differently, how would you have to change it?", but we will just be talking through it not writing new code.
+
+## What questions will I be asked and how should I answer?
+
+You will be asked three questions. We will ask you:
+
+### To introduce yourself
+
+We expect that you:
+
+- Say your name
+- Explain why you are applying to join the SDC
+  - Your background that makes the SDC relevant to you (this can be recent or long-term!)
+  - Your forward-looking hopes that makes the SDC relevant to you
+
+### To explain how one feature in any one of your three projects works
+
+We expect that you:
 
-## What questions will I be asked?
+- Could explain in high-level terms how a feature worked.
+- Could frame things both from a user-facing and developer-facing perspective.
+- Presented information in an intelligible order.
+- Didn't lose the interviewer, e.g. by going on a deep tangent, or by using terms the interviewer didn't understand (without checking).
 
-You will be asked to explain the code. You may be asked to:
+### To explain how some code in one of your three projects works
 
-1. Play computer and run the code in your head
-1. Explain what the state of the application is at different points in the code
-1. Define the function and meaning of different parts of the code
-1. Refactor the code to meet new requirements given by the interviewer
+We expect that you:
+
+- Could convincingly explain every line of code asked about.
+- Could make accurate predictions about values/state.
+- Tied explanation back to the feature / requirements being implemented.
+
+We are looking for conceptual understanding/sound mental model here, not rote learning.
+
+You must do _all_ of these things. But just like with demos, your answers should feel natural - it shouldn't feel like you're running through a list of bullet points you need to hit.
+
+We can ask you about any feature or code in any of your projects. It is not acceptable to say "I can't explain that because someone else wrote it".
+
+We expect you to be able to share your screen and show code from your projects in the interview.
 
 ## What happens next
 
-- Your interview will be recorded and scored against a rubric you can read before the interview.
+- Your interview will be recorded and scored against the rubric above.
 - You will not get feedback in the interview itself. You will be sent feedback within a few days of the interview.
 - If you passed, you will be invited to join the next [SDC](/sdc/).
 - If you failed, you will be given feedback and invited to discuss the best next steps for you.
-
-
-Once your interview is done, you are done. Join the wrap party and celebrate your hard work! What a journey! 🎉

common-content/en/module/checkpoint/mock-interview/index.md

@@ -0,0 +1,12 @@
++++
+title = "Mock Interview"
+time = 60
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Practicing, and getting feedback, will help you interview.
+
+You may want to do a mock interview before your real one. You can always ask in the [#cyf-interview-practice Slack channel](https://codeyourfutur-yov6609.slack.com/archives/C07PDUBM87P) for a mock interview with a volunteer. If you do, you should probably share with your mock interviewer what style of interview you're preparing for. Send them a link to [the day-plan](../day-plan/) which describes what you will be asked and what we're looking for in your answers.

org-cyf/content/checkpoint/sprints/2/_index.md

@@ -1,10 +1,10 @@
 +++
 title = 'Sprint 2'
-description = 'Demo your project; kick off the next group project'
+description = 'Demo your team work; kick off your individual project'
 layout = 'sprint'
-emoji= '🎽'
+emoji= '🏃🏾'
 menu_level = ['module']
 menu=['Checkpoint sprints']
 weight = 2
-theme = "Work in a team to deliver working software with tests"
+theme = "Build a complete project on your own"
 +++

org-cyf/content/checkpoint/sprints/2/backlog/index.md

@@ -4,5 +4,5 @@ layout = 'backlog'
 menu_level = ['sprint']
 weight = 2
 backlog= 'Checkpoint'
-backlog_filter='📅 Sprint 2'
+backlog_filter='📅 Sprint 3'
 +++

org-cyf/content/checkpoint/sprints/2/day-plan/index.md

@@ -5,38 +5,46 @@ menu_level = ['sprint']
 weight = 3
 [[blocks]]
 name="Energiser"
-src="energisers/blockers"
+src="energisers/wemoji"
 [[blocks]]
 name="Demo"
 src="module/checkpoint/demo"
 [[blocks]]
-name="Kickoff"
-src="module/checkpoint/kickoff"
-time=20
-[[blocks]]
 name="Morning break"
 src="blocks/morning-break"
 [[blocks]]
-name="Group Project: Days Calendar"
-src="https://github.com/CodeYourFuture/Checkpoint/tree/main/Project-Days-Calendar"
-time=40
+name="Solo project"
+src="module/checkpoint/solo-project"
+time=45
+[[blocks.nested.blocks]]
+name="Spaced Repetition Tracker"
+src="https://github.com/CodeYourFuture/Checkpoint/tree/main/Project-Spaced-Repetition-Tracker"
+time=0
+[[blocks.nested.blocks]]
+name="Music Data"
+src="https://github.com/CodeYourFuture/Checkpoint/tree/main/Project-Music-Data"
+time=0
+[[blocks.nested.blocks]]
+name="Codewars Leaderboard"
+src="https://github.com/CodeYourFuture/Checkpoint/tree/main/Project-Codewars-Leaderboard"
+time=0
 [[blocks]]
 name="Development"
-src="module/checkpoint/development"
-time="30"
+src="module/checkpoint/solo-development"
+time="60"
 [[blocks]]
 name="lunch"
 src="blocks/lunch"
 [[blocks]]
 name="Development"
-src="module/checkpoint/development"
+src="module/checkpoint/solo-development"
 time="75"
 [[blocks]]
 name="Afternoon break"
 src="blocks/afternoon-break"
 [[blocks]]
 name="Development"
-src="module/checkpoint/development"
+src="module/checkpoint/solo-development"
 time="75"
 [[blocks]]
 name="Wrap"

org-cyf/content/checkpoint/sprints/2/success/index.md

@@ -4,11 +4,11 @@ layout = 'success'
 menu_level = ['sprint']
 weight = 4
 backlog= 'Checkpoint'
-backlog_filter='📅 Sprint 2'
+backlog_filter='📅 Sprint 3'
 +++
 
-> Your key goal this sprint is to complete your team project.
+> Your key goal this sprint is to complete your solo project.
 
 You must submit a link to your deployed project, as well as your GitHub repo.
 
-You must be able to explain every line of code in your project, even ones you didn't write yourself.
+You must be able to explain every line of code in your project.

org-cyf/content/checkpoint/sprints/3/_index.md

@@ -1,10 +1,10 @@
 +++
 title = 'Sprint 3'
-description = 'Demo your team work; kick off your individual project'
+description = 'Demo your project; kick off the next group project'
 layout = 'sprint'
-emoji= '🏃🏾'
+emoji= '🎽'
 menu_level = ['module']
 menu=['Checkpoint sprints']
 weight = 3
-theme = "Build a complete project on your own"
+theme = "Work in a team to deliver working software with tests"
 +++

org-cyf/content/checkpoint/sprints/3/backlog/index.md

@@ -4,5 +4,5 @@ layout = 'backlog'
 menu_level = ['sprint']
 weight = 2
 backlog= 'Checkpoint'
-backlog_filter='📅 Sprint 3'
+backlog_filter='📅 Sprint 2'
 +++

org-cyf/content/checkpoint/sprints/3/day-plan/index.md

@@ -5,50 +5,38 @@ menu_level = ['sprint']
 weight = 3
 [[blocks]]
 name="Energiser"
-src="energisers/wemoji"
+src="energisers/blockers"
 [[blocks]]
 name="Demo"
 src="module/checkpoint/demo"
 [[blocks]]
+name="Kickoff"
+src="module/checkpoint/kickoff"
+time=20
+[[blocks]]
 name="Morning break"
 src="blocks/morning-break"
 [[blocks]]
-name="Solo project"
-src="module/checkpoint/solo-project"
-time=45
-[[blocks.nested.blocks]]
-name="Spaced Repetition Tracker"
-src="https://github.com/CodeYourFuture/Checkpoint/tree/main/Project-Spaced-Repetition-Tracker"
-time=0
-[[blocks.nested.blocks]]
-name="Music Data"
-src="https://github.com/CodeYourFuture/Checkpoint/tree/main/Project-Music-Data"
-time=0
-[[blocks.nested.blocks]]
-name="Codewars Leaderboard"
-src="https://github.com/CodeYourFuture/Checkpoint/tree/main/Project-Codewars-Leaderboard"
-time=0
-[[blocks.nested.blocks]]
-name="Spell Checker"
-src="https://github.com/CodeYourFuture/Checkpoint/tree/main/Project-Spell-Checker"
-time=0
+name="Group Project: Days Calendar"
+src="https://github.com/CodeYourFuture/Checkpoint/tree/main/Project-Days-Calendar"
+time=40
 [[blocks]]
 name="Development"
-src="module/checkpoint/solo-development"
-time="60"
+src="module/checkpoint/development"
+time="30"
 [[blocks]]
 name="lunch"
 src="blocks/lunch"
 [[blocks]]
 name="Development"
-src="module/checkpoint/solo-development"
+src="module/checkpoint/development"
 time="75"
 [[blocks]]
 name="Afternoon break"
 src="blocks/afternoon-break"
 [[blocks]]
 name="Development"
-src="module/checkpoint/solo-development"
+src="module/checkpoint/development"
 time="75"
 [[blocks]]
 name="Wrap"

org-cyf/content/checkpoint/sprints/3/success/index.md

@@ -4,11 +4,11 @@ layout = 'success'
 menu_level = ['sprint']
 weight = 4
 backlog= 'Checkpoint'
-backlog_filter='📅 Sprint 3'
+backlog_filter='📅 Sprint 2'
 +++
 
-> Your key goal this sprint is to complete your solo project.
+> Your key goal this sprint is to complete your team project.
 
 You must submit a link to your deployed project, as well as your GitHub repo.
 
-You must be able to explain every line of code in your project.
+You must be able to explain every line of code in your project, even ones you didn't write yourself.

org-cyf/content/checkpoint/sprints/4/day-plan/index.md

@@ -3,24 +3,9 @@ title = 'day-plan'
 layout = 'day-plan'
 menu_level = ['sprint']
 weight = 3
-[[blocks]]
-name="Energiser"
-src="energisers/fizz-buzz"
-[[blocks]]
-name="Demo"
-src="module/checkpoint/demo"
-[[blocks]]
-name="Morning break"
-src="blocks/morning-break"
+noRegister = true
 [[blocks]]
 name="Interviews"
 src="module/checkpoint/interviews"
-time=95
-[[blocks]]
-name="lunch"
-src="blocks/lunch"
-[[blocks]]
-name="Wrap Party"
-src="module/checkpoint/wrap-party"
-time=120
+time=240
 +++

org-cyf/content/checkpoint/sprints/4/prep/index.md

@@ -10,6 +10,9 @@ src="module/checkpoint/assessment"
 name="Interview tips"
 src="module/checkpoint/interview-tips"
 [[blocks]]
+name="Mock Interview"
+src="module/checkpoint/mock-interview"
+[[blocks]]
 name="Programming Pre-requisites"
 src="module/checkpoint/programming-prereqs"
 +++