Chapter 25 — Team project studio | Technologist Security governance, risk and compliance

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 25 — Team project studio

Lesson map

Lesson 25 published. Map, example, EX073.

flowchart TD
  N0["Learning outcomes"]
  N1["25.1 The brief"]
  N2["25.2 Peer review"]
  N3["25.3 Client presentation"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX073"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["25.1 The brief"]
  N2["25.2 Peer review"]
  N3["25.3 Client presentation"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX073"]

[Learning outcomes]
    |
    v
[25.1 The brief]
    |
    v
[25.2 Peer review]
    |
    v
[25.3 Client presentation]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX073]

Learning outcomes

You will (1) work in a team on a GRC deliverable; (2) divide work and review each other's output; (3) present to a client.

25.1 The brief

In the team studio, Priya's group is asked by Riverton to produce an onboarding pack for the three new clinics: a checklist for secure setup, a list of controls the clinic manager owns, evidence requirements and a short training session. The team has four members with different strengths: networks, documentation, training design and data. They agree roles, deadlines and a shared folder. Mr. Lind suggests that the data specialist check every evidence requirement can actually be produced by the new clinics' systems.

25.2 Peer review

Each member's work is reviewed by another before submission. Priya's evidence requirements are reviewed by the documentation specialist, who finds two terms used inconsistently. The training design is reviewed by Priya, who suggests adding a scenario about misdirected laboratory emails. Peer review catches errors and improves clarity. She learns that reviewing others' work is a skill in itself, requiring specific and respectful feedback. The misdirected laboratory email scenario draws on a risk Riverton has already recorded, so the training stays relevant.

25.3 Client presentation

The team presents to Riverton's operations manager and a clinic manager. They walk through the checklist and demonstrate the training scenario. The clinic manager asks for a version of the checklist on one page, which the team produces the next day. Priya learns that clients value practical usability, and that listening to feedback during a presentation is as important as delivering it well. A one-page checklist is more likely to be used at a busy new clinic than a longer document.

Worked example

Priya's team produces a new-clinic onboarding pack, uses peer review to catch inconsistencies and adapts the checklist after client feedback.

Synthetic case. The project is synthetic.

Errors and limits

Team dynamics vary. Client requests can expand scope.

Exercises

EX073 — Pack contents. What does the onboarding pack contain? Rubric: 3 = setup checklist, manager-owned controls, evidence requirements, training;; 2 = four parts;; 1 = vague;; 0 = none.
EX074 — Review finding. What did peer review find in Priya's work? Rubric: 3 = two terms used inconsistently;; 2 = inconsistency;; 1 = vague;; 0 = none.
EX075 — Client request. What did the clinic manager ask for? Rubric: 3 = a one-page checklist;; 2 = one page;; 1 = vague;; 0 = none.

Synthesis

Team projects succeed through clear roles, peer review and responsiveness to clients.

Continue studying — chapter 25 of 30

← Chapter 24 (draft) · Course chapter index · Chapter 26 (draft) →