Combine and clarify demo rubrics

Before, we had two nearly-identical copies, one for trainees and one
for volunteers. Now we have one shared rubric.

Author: illicitonion

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. If they haven't used the minimum time, they missed this too.</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/demo/index.md

@@ -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. You must be presenting for at least the minimum 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>