What is Security Between Us?

Decisions related to security rarely come with a “You are now making a security decision” warning. To create secure code, developers need to take into account factors from the broader context of work, including influences from the team, department, the broader organisation and other stakeholders.

This workshop was developed out of fieldwork undertaken by the Motivating Jenny team. In it, pairs of developers look at what security means in the context of everyday projects and tasks.

Why should I use this?

It allows developers to build up a rich picture of their environment, especially people, processes and technology and the relationship between them. Participants trade information about how things work on projects, in teams and in departments.

This workshop often serves to identify what security practices are working well, and what can be improved.

When can it be used?

  • Onboarding staff or a new team
  • Retrospectives
  • At the start of an iteration, along with the design process.

To run this activity, you need:

  • 60 minutes
  • Two or more participants
  • A facilitator
  • Some Lego.
  • A printed set of materials. See OrganiserInstructions.pdfin the download pack.
Security Security Between Us
A diagram of personal horizons and security responses.

Lopez, T., Weir, C., Tun, T., Cooper, H., Bandara, A., Levine, M., Nuseibeh, B. and Sharp, H. (2020) ‘Security Between Us’, figshare [Online]. DOI: 10.21954/ou.rd.12213146 (Accessed Day Month Year).