<p><em>Disclosure - I have not worked in proper ("Academia") research and science projects.</em></p>

<p>DevOps should be just fine for researchers. As in the commercial world, the interesting bit will be to pick the line where the DevOps teams start and where the lower level base ops begins. This is not a contradiction. You may still have a dedicated ops team which provides the hardware, networking, OS, container management (Kubernetes ect. if you have something like this) and so on.</p>

<p>The most crucial part is that these ops guys now provide the <em>base</em> for the other teams. This means there is <em>not</em> a hand-over of software between the other teams and ops. Ops has the responsibility to provide the DevOps teams with an infrastructure (or platform, whatever you may call it in your case) so they can do their slightly higher-level stuff in a self-sufficient manner. The base ops team would do the hard lifting (i.e., IAM, license stuff, security issues etc.).</p>

<p>There is a plethora of possible ways to structure this. E.g., if you are in a non-techy research field (say, statistics, where people know <code>R</code> but nothing much else), you will have a different structure than if your researchers are hardcore coders/OS experts (say, the VR department where researchers program GPUs etc.).</p>

CC BY-SA 4.0
2019-03-28T17:07:34.297Z
2019-03-28T17:07:34.297Z
AnoE
<p>Is DevOps methodologically anyhow different or even applicable in the academia field if used in research and science projects?</p>

CC BY-SA 4.0
2019-03-28T12:21:34.257Z
so the ops organizations remain to watch identity management, budget and security controls? Otherwise reseachers have to become cost aware of any experiment iteration being it CI job or model training.
Ta Mu
CC BY-SA 4.0
2019-03-28T17:09:15.317Z
I've added an answer now, @Peter.
AnoE
CC BY-SA 4.0
2019-03-28T19:02:34.627Z
This is such a vague question. Research and science varies from clinical trials and launching satellites down to comsci projects by PhD students. For the question to be a good fit it should be specific and not something that so vague that any answer couldn't be identified as being accurate or not.
simbo1905
CC BY-SA 4.0
2019-05-10T05:29:03.200Z
Still I find Anoe's answer very satisfying.
Ta Mu
<culture><academia>
DevOps in research and science projects?
Ta Mu
# DevOps in research and science projects?

(Asked by: username_0 on 2019-03-28)

Is DevOps methodologically anyhow different or even applicable in the academia field if used in research and science projects?

**Tags:** culture, academia

> **Comments:**
> **username_0**: so the ops organizations remain to watch identity management, budget and security controls? Otherwise reseachers have to become cost aware of any experiment iteration being it CI job or model training.  
> **username_1**: I've added an answer now, @Peter.  
> **username_2**: This is such a vague question. Research and science varies from clinical trials and launching satellites down to comsci projects by PhD students. For the question to be a good fit it should be specific and not something that so vague that any answer couldn't be identified as being accurate or not.  
> **username_0**: Still I find Anoe's answer very satisfying.  

---

## 1 answers

### Answer by username_1 on 2019-03-28. Score: 2 | Accepted answer

*Disclosure - I have not worked in proper ("Academia") research and science projects.*

DevOps should be just fine for researchers. As in the commercial world, the interesting bit will be to pick the line where the DevOps teams start and where the lower level base ops begins. This is not a contradiction. You may still have a dedicated ops team which provides the hardware, networking, OS, container management (Kubernetes ect. if you have something like this) and so on.

The most crucial part is that these ops guys now provide the *base* for the other teams. This means there is *not* a hand-over of software between the other teams and ops. Ops has the responsibility to provide the DevOps teams with an infrastructure (or platform, whatever you may call it in your case) so they can do their slightly higher-level stuff in a self-sufficient manner. The base ops team would do the hard lifting (i.e., IAM, license stuff, security issues etc.).

There is a plethora of possible ways to structure this. E.g., if you are in a non-techy research field (say, statistics, where people know `R` but nothing much else), you will have a different structure than if your researchers are hardcore coders/OS experts (say, the VR department where researchers program GPUs etc.).


---

