From 17a1d7126bae2282845cd02e896a12d2514c9fc2 Mon Sep 17 00:00:00 2001 From: Liam J Berrisford Date: Mon, 14 Jul 2025 10:44:36 +0100 Subject: [PATCH 1/3] add new details to leader role details --- contributing/roles.ipynb | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/contributing/roles.ipynb b/contributing/roles.ipynb index b0a513ac..c40ae4af 100644 --- a/contributing/roles.ipynb +++ b/contributing/roles.ipynb @@ -72,6 +72,7 @@ "- Coordinate with the other members of the workshop delivery team and ensure that they are clear on their roles and know when and where to attend on the day. \n", "- Attend a pre-workshop meeting of up to 30 minutes with the rest of the delivery team. Experienced workshop leads may be happy to organise and host this meeting. Otherwise, programme management can facilitate. \n", "- Review the pre-course questionnaire information for participants to familiarise themselves with the current experience level and expectations of the participants. \n", + "- Familiarise yourself with the learning objectives for the session and plan to deliver the workshop in a way that ensures these are met to the best of your ability. Remember, the priority is achieving the intent (‘spirit of the law’) behind the objectives rather than covering every single piece of content or activity.\n", "\n", "### During a workshop \n", "- Arrive 10-15 minutes before the scheduled start of the workshop, ensure the IT is setup appropriately, and display the welcome slides with QR codes. \n", @@ -84,6 +85,9 @@ " - Share the Code of Conduct and note that attendance is an agreement to adhere by this. \n", "- Deliver the course materials using a methodology appropriate to the learning objectives. For novices, this is predominately by live coding. \n", "- Schedule regular breaks (one/two for a three-hour session). \n", + "- Adapt to the Group: Each cohort is unique. Be flexible with timing—extend or shorten activities as needed to match the group’s pace and engagement. The provided activities are guides to help you keep on track with timing; feel free to adjust as necessary.\n", + "- Prioritise Quality Over Quantity: It is better to cover fewer topics and ensure participants achieve a meaningful understanding, rather than rushing to touch on everything. If the group is especially engaged with an exercise, allow more time and feel free to skip or condense other activities.\n", + "- Monitor Participant Engagement: Actively observe the group’s energy and participation. Use breaks strategically and encourage open discussions, group work, or partner activities to foster engagement and peer learning.\n", "- Leave adequate time to wrap up the workshop: \n", " - Summarise the content of the workshop. \n", " - Signpost to next steps (e.g. future workshops in the programme that follow on) and where to access help after the end of the workshop (e.g. Slack channel). \n", From f0feeeece6f673f2c5430d3cb67e66c307e5f6fc Mon Sep 17 00:00:00 2001 From: Liam J Berrisford Date: Fri, 8 Aug 2025 11:05:17 +0100 Subject: [PATCH 2/3] Add Fliss review changes --- contributing/roles.ipynb | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/contributing/roles.ipynb b/contributing/roles.ipynb index c40ae4af..ce1fea38 100644 --- a/contributing/roles.ipynb +++ b/contributing/roles.ipynb @@ -67,12 +67,13 @@ "\n", "### In advance of the workshop \n", "- Review the pre-existing course materials and notify programme management if there are any concerns with these. The workshop lead is not expected to create course materials; this is handled by a different role. Similarly, the workshop lead should not revise the materials without first consulting the programme management. \n", + "- Familiarise yourself with the learning objectives for the session and plan to deliver the workshop in a way that ensures these are met to the best of your ability. The priority is achieving the intent behind the objectives rather than covering every single piece of content or activity.\n", "- Review reports from previous deliveries of the same workshop. \n", "- Decide whether a troubleshooting session for installation queries will be held and liaise with programme management to communicate this to participants. \n", "- Coordinate with the other members of the workshop delivery team and ensure that they are clear on their roles and know when and where to attend on the day. \n", "- Attend a pre-workshop meeting of up to 30 minutes with the rest of the delivery team. Experienced workshop leads may be happy to organise and host this meeting. Otherwise, programme management can facilitate. \n", "- Review the pre-course questionnaire information for participants to familiarise themselves with the current experience level and expectations of the participants. \n", - "- Familiarise yourself with the learning objectives for the session and plan to deliver the workshop in a way that ensures these are met to the best of your ability. Remember, the priority is achieving the intent (‘spirit of the law’) behind the objectives rather than covering every single piece of content or activity.\n", + "\n", "\n", "### During a workshop \n", "- Arrive 10-15 minutes before the scheduled start of the workshop, ensure the IT is setup appropriately, and display the welcome slides with QR codes. \n", @@ -81,16 +82,16 @@ " - Ask participants to add their name to the participants list. \n", " - Share the learning objectives of the workshop and the delivery method. \n", " - Reference it is part of the CfRR programme. \n", - " - Acknowledge the contribution of the Research Software & Analytics Team, IDSAI and community of researchers who deliver this training. \n", + " - Acknowledge the contribution of the Research Software & Analytics Team and community of researchers who deliver this training. \n", " - Share the Code of Conduct and note that attendance is an agreement to adhere by this. \n", "- Deliver the course materials using a methodology appropriate to the learning objectives. For novices, this is predominately by live coding. \n", "- Schedule regular breaks (one/two for a three-hour session). \n", - "- Adapt to the Group: Each cohort is unique. Be flexible with timing—extend or shorten activities as needed to match the group’s pace and engagement. The provided activities are guides to help you keep on track with timing; feel free to adjust as necessary.\n", + "- Be flexible with timing, by extending or shortening activities as needed to match the group’s pace and engagement.\n", "- Prioritise Quality Over Quantity: It is better to cover fewer topics and ensure participants achieve a meaningful understanding, rather than rushing to touch on everything. If the group is especially engaged with an exercise, allow more time and feel free to skip or condense other activities.\n", "- Monitor Participant Engagement: Actively observe the group’s energy and participation. Use breaks strategically and encourage open discussions, group work, or partner activities to foster engagement and peer learning.\n", "- Leave adequate time to wrap up the workshop: \n", " - Summarise the content of the workshop. \n", - " - Signpost to next steps (e.g. future workshops in the programme that follow on) and where to access help after the end of the workshop (e.g. Slack channel). \n", + " - Signpost to next steps (e.g. future workshops in the programme that follow on) and where to access help after the end of the workshop (e.g. Research Coding Community on Teams, [Signup Page](community.ipynb)). \n", " - Highlight the importance of the feedback survey. \n", " - Thank participants for supporting the programme. \n", "\n", From 498d1978c66e33c7a72a54d9d94f9cb2b9e3df6b Mon Sep 17 00:00:00 2001 From: Liam J Berrisford Date: Fri, 8 Aug 2025 12:50:41 +0100 Subject: [PATCH 3/3] Update bullet point ordering --- contributing/roles.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributing/roles.ipynb b/contributing/roles.ipynb index ce1fea38..2ba7b2fa 100644 --- a/contributing/roles.ipynb +++ b/contributing/roles.ipynb @@ -85,10 +85,10 @@ " - Acknowledge the contribution of the Research Software & Analytics Team and community of researchers who deliver this training. \n", " - Share the Code of Conduct and note that attendance is an agreement to adhere by this. \n", "- Deliver the course materials using a methodology appropriate to the learning objectives. For novices, this is predominately by live coding. \n", - "- Schedule regular breaks (one/two for a three-hour session). \n", "- Be flexible with timing, by extending or shortening activities as needed to match the group’s pace and engagement.\n", "- Prioritise Quality Over Quantity: It is better to cover fewer topics and ensure participants achieve a meaningful understanding, rather than rushing to touch on everything. If the group is especially engaged with an exercise, allow more time and feel free to skip or condense other activities.\n", "- Monitor Participant Engagement: Actively observe the group’s energy and participation. Use breaks strategically and encourage open discussions, group work, or partner activities to foster engagement and peer learning.\n", + "- Schedule regular breaks (one/two for a three-hour session). \n", "- Leave adequate time to wrap up the workshop: \n", " - Summarise the content of the workshop. \n", " - Signpost to next steps (e.g. future workshops in the programme that follow on) and where to access help after the end of the workshop (e.g. Research Coding Community on Teams, [Signup Page](community.ipynb)). \n",