Document and manage all TRESA processes

[Davsarper]

Goal Title

What will this work achieve?
Smooth running of Turing TRE deployments

Description

• Work with projects to improve current documentation
• Ensure all standard operating procedures are recorded

Definition of Done

When will this be considered as succesfully completed?
Ongoing

Details

• RACI
  • Accountable team or person: TRESA
  • Responsible team or person: RAM, RPM
  • Informed and consulted people: project teams, PMU
• Estimated effort
  • RAM: Can be incorporated under accountability for Documentation management #32
  • RPM: time for support here can be included with TRESA establish cost recovery process #55
• High effort
• Story points (Above 10, sum of monthly issues effort)

Resourcing

August

• REG: 0.1

Task and issue breakdown

Breakdown in specific tasks of maximum a month duration, tasks and issues may be added as necessary
Issues may span across repositories when necessary

• issue alan-turing-institute/data-safe-haven-team#X
• issue alan-turing-institute/data-safe-haven#X
• issue alan-turing-institute/trusted-research
• issue sa-tre/satre-specification#X
• issue sa-tre/satre-team#X

Checklist

• This Story have been agreed with project members, it tackles prioritised work
  • If not: Label as ForPrioritisation so it discussed in the next monthly meeting, do not set a status
• I have included this Story in the agreed upon Milestone, set status as Planned
  • If not: set status as Backlog, to be Planned via weekly meetings/discussions
• The work to be done is likely to span over a month
• I have broken down the work in monthly issues and added them above
• I have labeled this issue according to its main project: SATRE, TRESA, CORE DSH (ELA) or other (please agree and create a new label if necessary)
• I have stimated the total effort and added it in the body (under Details) but left the issue field blank

[Davsarper]

@JimMadge @harisood will this story cover what we plan to do in the new year? Probably needs to reflect processes improvement rather than only documenting them in the title.
We can complete the main comment together when we plan

[JimMadge]

This sounds to me like the continuous process of managing processes.

What I'm imagining is more like a sprint to,

1. Assess the current state
2. Codify the responsibilities
3. Establish the process for having input from TRESA, dev team, data protection
4. Identify and prioritise improvements (but making those changes it another piece of work)

[harisood]

Agree with @JimMadge, I would just drop the 'Document and'

[Davsarper]

I shall create a new story then

[harisood]

Jan planning

This is a focus of this month, to hand over this stuff to TRESA

Resourcing

• REG
  • 0.2 @JimMadge
• RAM: 0.1
• RPM: 0.2

[Davsarper]

February: as TRESA owns the processes is not up to DSH team to prioritise. re-evaluate how we interact and keep track of actions