(project_team_guidance)=

# Project team guidance

Choose a member of the project who is a staff member at Turing to have overall responsibility for liasing with {ref}`role_tresa` on matters relating to the operation of the TRE.
This person should bookmark these docs for reference and take responsibility for the completion of the project team tasks and responsibilities which are summarised below.

{ref}`role_tresa` will take responsibility for managing the TRE and tracking the completion of all operational tasks, but project teams interested to learn more can view the full list of tasks here: {ref}`tasks`.
Here is a high level look at the TRE project lifecycle:

```{image} ../images/lifecycle-simplified.drawio.svg
:alt: Project lifecycle simplified
:align: center
```

## Getting started

The initial tasks that the TRESA team need the project team to carry out are listed below.
Take a look through these tasks and consider the time required for set up and when you will have time to perform them.
As the project progresses, the TRESA team will let you know if they need you to carry out other actions from the complete list of {ref}`tasks`.

### TRE details and configuration

These actions are about getting your trusted research environment (TRE) set up and ensuring that you can pay for it.

1. {ref}`project_initialisation`
2. {ref}`project_costing`
3. {ref}`submit_project_details`

### Setting up TRE user accounts

These actions are about training users and giving them access to the TRE.

1. {ref}`collect_user_information`
2. {ref}`monitor_user_access_requirements`

### Data ingress

These actions are about bringing code or data into the TRE.

1. {ref}`arrange_data_ingress`
2. {ref}`validate_data_ingress`

## During the project

These actions are about analysing data inside the TRE.

1. {ref}`data_analysis`
2. {ref}`support_optout` (if applicable)

- Communicate to {ref}`role_tresa` about any issues you may be facing with the TRE.
- You may wish to set up a Slack channel with key members of the project team and TRESA for quicker communication.

## Data egress

These actions are about bringing code or data out of the TRE.

1. {ref}`arrange_data_egress`

## Project end

These actions are about shutting the SRE down and securely deleting any data.

1. {ref}`request_teardown`