# AH Progress

## Goals

Top level points are the goals and sub points are what some thoughts on would/could provide this.
- Have more impactful involvement in REG/Turing projects and direction
- Scoping projects
- More responsibilities
- Leading a project
- Being point of contact for collaborators
- Feel trusted and respected

### Misc Thoughts
- Martin made a comment on the axes of importance to me
- I feel that it's a x=y situation. Where the most important work is the most impactful, is the most meaningful to me, and also the most valuable to the team.
- One view I have on seniority is that it represents not just an acknowledgement of technical skill and ability, but also on taking on an increased responsibility in shaping, growing, improving and nurturing the team. Hence, the above point

## Relevent information on what is required for career growth

From https://github.com/alan-turing-institute/Hut23/discussions/1163
>Q: What's the delta between senior and standard?
>>A: See the list at the bottom of this text box for a list of elements from the current Senior job description that are over and above those required of the Standard level role. These are broadly speaking: Development of others (could be on projects, does not have to be a REG person, could also be helping someone at or above your level); Comfort with ability to pick up an arbitrary project; Comfort with leading a project, including managing relationship with PIs and planning; Technical maturity, with the ability to guide the work of others and develop them in your areas of expertise.

Reading between the lines this translates to:

- Development of others
- Comfort with ability to pick up an arbitrary project
- Comfort with leading a project
- Managing relationship with PIs and planning
- Technical maturity

Additionally:

>The following are things in the Senior role description that are over and above those required of the Standard level role.

>>- Provide technical project management and leadership for 1-3 research projects, ensuring successful outcomes, liaising with clients and colleagues to understand and prioritise project goals, and balancing client value with research outputs.
>>- Act as the group lead for a particular Turing Programme, helping to coordinate the partnership and taking ownership of the associated challenge areas.
>>- Develop new projects in conjunction with colleagues, authoring research proposals and agreeing involvement for the group in activities across the institute.
>>- Line manage 1-3 other staff within the group, supporting their career development aspirations.
>>- Experience leading a project to a successful conclusion.
>>- Either experience in making or evaluating the case for new projects (for instance, authoring or evaluating research proposals or business cases) or experience of managing, prioritising and resourcing a project portfolio.
>>- Experience mentoring and evaluating the work of others. (Formal line management experience is not essential, but such applicants should be able to show significant evidence of informal mentorship.)
>>- Demonstrable experience managing conflict and resolving stakeholder tensions (desirable).

## Aoife Self-Evaluation

With respect to the information given above I feel the following things have been and can be demonstrated:

- [x] Development of others
- Turing Mentor Scheme
- Always thinking of new ways to make it easier to share knowledge in REG, .e.g, starting the hut23-askaway slack channel
- Outside Turing work (teaching/lecturing)
- Acted as a `buddy` for a few new starters
- Make effort to reach out to all new starters and have informal chats to offer help or guidence
- Voluenteering for REG related training
- Leading RDS modules
- Appearing on panels at Turing events
- Active participation in EDI service area
- Pushing and investigating external collaborations with under-represented groups
- Active participation in answering quesions from others in REG and wider Turing
- [x] Comfort with ability to pick up an arbitrary project
- Two most recent projects are excellent examples
- Both very short projects
- Both Poorly defined in terms of REG involvement
- Found ways in both projects to have a meaningful impact
- [x] Comfort with leading a project
- Pandemia project allowed me to take on an management and organisational role
- Gave feedback on potential issues early and often with the REG lead
- Organised task lists and coordinated how we (REG) would split tasks and what they would be
- SSI Fellowship is fully driven by me
- Included speaking with and coordinating with REG and scoping ideas
- e.g., could it tie in with existing REG training courses, meetings to discuss if Turing's binder systems would be appropriate etc.
- A scoping presentation and report were made for this and approved by the SSI
- Less relevent but my previous roles have afforded me many opportunities to do this too!
- [x] Managing relationship with PIs and planning
- Again, the Pandemia project is a great example of this.
- Could have easily become an awkward situation with project generally being in a much worse state than what was told to REG during scoping
- Formed an excellent working relationshop with collaborator
- Made clear reasons for issues (technical implementations mostly)
- Negotiated routinely what REG should/could do
- Came to agreements where everyone was content with what was being done
- The DYME project also resulted in REG performing work which was not initially clear
- We kept in constant communication with collaborators and explained choices and reasoning for what we could do
- Formed a wonderful working relationship here too.
- Whilst not quite appropriate to ask, I am confident that these collaborators on both projects would be happy with REG invovlement and contributions.
- Again, these projects were very short and as such required constant planning and being adaptable.
- [x] Technical maturity
- Pick up new not just technologies quickly, but make use of them and push their usefulness in projects
- Learnt Docker scripting and created a setup for reproducible simulations for DYME
- Learnt AZURE systems, cost analysis, storage solutions, batch processing etc.
- Fast adaption of novel scientific methods without prior experience:
- Understood epidemic modelling
- Use of scientific geography softwares and standards
- Climate modelling standards and pipelines
- To the point of now contributing to a review paper
- and drafting a conference proceedings paper
- https://cambridge-iccs.github.io/climate-informatics-2023/

Where I would agree additional demonstrations could be made is in:

- [x] Acting as a lead in a challenge area
- [x] Develop new projects
- [ ] Line manage within REG
- [ ] Project scoping

## Aoife Actions
- Organise the HDR UK internship
- Meet with May about the health programme

## REG Actions
- Salary bump
- Exploring other areas for Aoife to demonstrate requirements for senior