---
# System prepended metadata

title: Needs analysis workshop - Planning

---

# Needs analysis workshop - Planning 

:::info
**Date**: 25 January 2023, 2-4 pm [JR: 26th/27th might be easier for me if that's OK]
**Venue**: In person
**Attendees**: skills (MN, VM, SN) amd REG people (James R, James G, Matt Cradock, Gabriel Hanganu, Lydia) from all seniority levels (add Jim, someone senior?)/ In a follow up session: RAMs, ARC, TRFs etc, research computing 
**Format**: 2 long sessions in small groups to brainstorm ideas for the 2 main tasks

**Goals**
- identify gaps at the landscape level and assess where the Turing is well placed to provide expertise and develop training  
- collate skills and knowledge gaps identified within the RSE / RDS hiring process (for those unsuccessful) and align them with the expertise areas
- match gaps with emerging strategical priorities regarding science, innovation and skills 

**Deliverables**
- build a learning pathway chart for different target audiences, using open access resources
- one output could be expected prerequisite level for those taking training courses at the Turing
- designing a curriculum of modules (grouping related topics into modules)
    - Note that RSE/RDS/RCE related modules will be only part of a larger offering
:::

Things to look at
- target audiences / learner personas 
- improvements, topic gaps etc within the current course provision (focus on RSE / RDS)
- open access resources and courses for different needs 
- build a catalogue of go-to Turing people for different skills and knowledge areas
    - cf. Nick Mann's idea for short videos on AI/ML topics ending with "talk to this person to find out more"
- RSE / RDS courses and evaluate the learning outcomes, prerequisites etc. 



## Planning meeting 25 Jan 2023

### Learner personas
- AI & DS professionals 
    - fundamental research
    - applied research
- domain experts with high analytical skills
    - academia -> industry transition
    - transferrable skills
- business leaders / exec *(separate session)
    - best practice



### Format 

- Pre-reading (skimming): Outcomes & Objectives from strategy
    - share all questions in advance and encourage people to come with ideas already
- (PART 1: Personas: 45 mins including intro) individual groups to look at different personas, then rotate
    - what support do they have and need in their organisation?
    - what are the prereqs and lowest level for them to be effective (give context and examples)
- Break: 10-15 mins
- (PART 2: What can we offer? 45-50 mins ) 
    - When REG recruit, what are applicants lacking?
        - looking for collaboration
        - looking for adaptable generalists
    - what are the strengths in REG that we could capitalise on?
    - what skills should we be teaching to help people progress (e.g. move from junior to standard within REG)?
    - what are the skills you wish others had to help you work effectively together?
    - What are some skills we'll wish we had in 2 years
    - what are some REG good practices worth sharing more widely
    - How can we get ahead of the curve and start building those skills now
- Wrap up: 5 mins    
```
- idea to run it more than once; first time with REG only, then open to other Turing people 
- Miro session with 10 mins individual ideas + 15 mins group discussions & consolidation
```

Fully remote, 2h


Attendees:
Lydia F
Matt C
Gabriel H
Jim M
James G
James R
Vera
Mishka
Sarah 

## Ways of working together 

- break it down in sprints with intense work periods // week or month allocation
- dedicated project lead for each agreed project 
- requirement for a jointly accessbile project management system
    - GitHub project boards
- presentation arranged by Vera on agile scrum methodology 

Dates options:
- 24th Feb: 10-12 pm
- 27th Feb: 10-12 pm
- 28th Feb: 2-4 pm 


Actions
- [x] - find agile expert on GitHub 
- [x] - identify best date for the target audience 
- [ ] - tidy up info page (this or a new HackMD)