Assessments

Jon Reades - j.reades@ucl.ac.uk

1st October 2026

The Assessments

  1. Group Work
    • Briefing (50%)
    • Code (35%)
  2. Peer Evaluation (15%)

Assessment #1

Overview

The reproducible analysis and briefing will be developed as part of a group and has two components:

  1. The briefing (50%, submitted as a PDF file): how do the answers written by the group engage with the set questions through a mix of literature, critical thinking, and data analysis?
  2. The code (35%, submitted as a QMD file): how well does the group’s code transfer to a ‘clean’ environment on a different computer?

These are submitted separately to two separate submission areas. Only one person needs to submit on behalf of the group.

In-Class Feedback

Because the format is novel, and also entails using Quarto, in Weeks 7 to 9 I will randomly select a group to present their (draft) answer to that week’s question in class.

  • Formative feedback will be provided in class on the quality of the response.
  • If the selected group has not prepared an answer then no formative feedback will be provided for that question.
  • It is not necessary that you have iPython notebook/Quarto outputs to-hand, though it will clearly help quite a bit.

This is intended to ensure that: a) you are doing the thinking and reading to progress towards submission; and b) you are learning how to use Quarto.

Data

Process

  • Over Reading Week you should start a literature scan in order to identify relevant approaches, policies, and findings. The module bibliography might help get you started, but it is not exhaustive.
  • Do not start trying to tackle the data analysis components of any of the questions until we have covered Pandas in Week 6.
  • Do not start trying to work directly with Quarto until we have covered Text in Week 8. Use iPython to create a exploratory notebooks and then transfer only the necessary bits of code and commentary as you develop familiarity with Quarto.
  • So from Week 9 you will want to be working primarily in Quarto to prepare the project submission, even as other members of the group/you continue to to use notebooks to test out ideas and undertake E(S)DA.

Resources

  • A template has been provided. By default it generates both PDF and HTML output, but please only submit the PDF
  • A reproducibility rubric explaining our expectations in greater detail.
  • A briefing rubric explaining our expectations in greater detail.
  • The module’s AI policy: what is and isn’t permitted, and how to declare any use.

Assessment #2

Overview

We know that people contribute differently to groups or, sometimes, not at all. This self- and peer-assessment seeks to quantify that contribution while also prompting you to reflect on what you contributed to your group and the wider dynamics of working as part of a team.

  • You will score your own contribution and provide a brief commentary.
  • You will also score everyone else’s contribution and provide brief feedback.

This assessment should not take more than 30 minutes in total.

When is it due?

  • Tuesday, 15 December 2026 @ 15:001

Where do I access it?

Time to Organise!

You are aiming for a group of no more than five:

  • If you are in a group of less than four you may be partnered with students in another practical session to make a ‘full strength’ group of up to five.
  • In this case, you can ask to be reallocated to a mutually convenient practical session so that you are not penalised by being unable to work together.
  • I would encourage you to start sitting and working together, and for one of you to set up and share a private GitHub repo.

And remember: talk about how you want your group to work! See: Group Working talk.1

Check-In & Signup

Checkpoint 1 Survey

Group Signup Form

Questions?

References