Answers: <p>I think we need to view this in the larger context of Flow and Systems Thinking which is one of the core values of DevOps.</p>
  
  <ol>
  <li>Specifically, DevOps Values require an understanding that each individual is part of a larger system and work toward increasing the flow of value through that system to the customer.</li>
  <li>DevOps also focuses on helping the organization set a shared vision and work incrementally and collaboratively on achieving that vision.</li>
  </ol>
  
  <p>In such a scenario, the focus needs to shift from "technology-specific silos" to "cross functional teams". And each DevOps practitioner needs to achieve a T-Shaped Skillset with core as well as shared responsibilities.</p>
  
  <p><strong>So, to answer your question:</strong></p>
  
  <blockquote>
    <p>Does DevOps really mean you are using another service so you have to manage that service as well?</p>
  </blockquote>
  
  <p>I think it depends.</p>
  
  <p>If your being able to manage the service leads to <em>increased flow of work through the pipeline to the customer</em> then yes.</p>
  
  <p>If however, it leads to you becoming a bottleneck or constraint to flow (perhaps due to you becoming overloaded with additional responsibilities), then no.</p>
  
  <p>If you are able to share this responsibility with others than manage the service (and have a Systems and Flow mindset), and <em>collaborate</em> with them so that none of you get too overloaded with work to become a constraint to flow, then yes.</p>
  
  <p>References:</p>
  
  <ol>
  <li><a href="https://itrevolution.com/the-three-ways-principles-underpinning-devops/" rel="noreferrer">DevOps Values</a></li>
  <li><a href="https://devops.com/adding-accountability-you-build-you-run/" rel="noreferrer">YBI/YRI</a></li>
  <li><a href="https://devops.com/introductiontodevops/" rel="noreferrer">What is DevOps</a></li>
  <li><a href="https://puppet.com/blog/what%E2%80%99s-best-team-structure-for-devops-success" rel="noreferrer">Cross-Functional Teams and DevOps</a></li>
  </ol>
  
Answers: CC BY-SA 3.0
Answers: 2018-04-13T10:50:01.210Z
Answers: Thank you for those insights, especially pointing towards _increasing the flow of value_ which helps as a rule of thumb
Answers: Hans Sperker
Answers: CC BY-SA 3.0
Answers: 2018-04-13T14:30:03.043Z
Answers: Or p-shaped. :)
Answers: 030
Answers: CC BY-SA 3.0
Answers: 2018-04-13T15:20:12.010Z
Answers: @030 I wonder how that would look :)
Answers: Vish
Answers: CC BY-SA 3.0
Answers: 2018-04-16T05:42:12.113Z
Answers: I think pi-shaped is more appropriate :-D
Answers: Hans Sperker
Answers: CC BY-SA 3.0
Answers: 2018-04-16T06:10:04.570Z
Answers: Hey, there's another `terminology` question you can ask - What's the appropriate shape to describe the skillsets required by a DevOps practitioner? :)
Answers: Vish
Answers: CC BY-SA 3.0
Answers: 2018-04-16T09:01:41.433Z
Answers: A better question IMHO would be: What is the bare minimum of rights and privileges (e.g. root on a system, write access, ...) one needs to perform DevOps tasks
Answers: Hans Sperker
Answers: CC BY-SA 4.0
Answers: 2021-06-14T11:33:43.083Z
Answers: @hans, ah yes! π has two legs. Full Stack ;)
Answers: Steven Shaw
Answers: CC BY-SA 3.0
Answers: 2018-04-13T08:17:06.900Z
Answers: 2018-04-13T08:17:06.900Z
Answers: Vish
Body: <p>As a member of a small agile development team developing an application heavily relying on Kafka I wonder what implications the DevOps paradigm of <em>You build it, you run it</em> has regarding running and maintaining a shared service like Kafka used by other teams as well.</p>
  
  <p>Does the <em>You build it, you run it</em> not only revolve around our application?</p>
  
  <p>Does DevOps really mean <em>you are using another service so you have to manage that service as well</em>?</p>
  
Comments: CC BY-SA 3.0
Comments: 2018-04-13T14:32:40.210Z
Comments: Try to write and share processes with other team members, process feedback and try to let them do tasks as well to promote interdependency.
Comments: 030
Tags: <terminology><sre>
Title: Who is responsible for running and maintaining shared services in DevOps
UserDisplayName: Hans Sperker
ThreadText: # Who is responsible for running and maintaining shared services in DevOps
  
  (Asked by: username_0 on 2018-04-13)
  
  As a member of a small agile development team developing an application heavily relying on Kafka I wonder what implications the DevOps paradigm of *You build it, you run it* has regarding running and maintaining a shared service like Kafka used by other teams as well.
  
  Does the *You build it, you run it* not only revolve around our application?
  
  Does DevOps really mean *you are using another service so you have to manage that service as well*?
  
  **Tags:** terminology, sre
  
  > **Comments:**
  > **username_1**: Try to write and share processes with other team members, process feedback and try to let them do tasks as well to promote interdependency.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2018-04-13. Score: 5 | Accepted answer
  
  I think we need to view this in the larger context of Flow and Systems Thinking which is one of the core values of DevOps.
  
  1. Specifically, DevOps Values require an understanding that each individual is part of a larger system and work toward increasing the flow of value through that system to the customer.
  2. DevOps also focuses on helping the organization set a shared vision and work incrementally and collaboratively on achieving that vision.
  
  In such a scenario, the focus needs to shift from "technology-specific silos" to "cross functional teams". And each DevOps practitioner needs to achieve a T-Shaped Skillset with core as well as shared responsibilities.
  
  **So, to answer your question:**
  
  > Does DevOps really mean you are using another service so you have to manage that service as well?
  
  I think it depends.
  
  If your being able to manage the service leads to *increased flow of work through the pipeline to the customer* then yes.
  
  If however, it leads to you becoming a bottleneck or constraint to flow (perhaps due to you becoming overloaded with additional responsibilities), then no.
  
  If you are able to share this responsibility with others than manage the service (and have a Systems and Flow mindset), and *collaborate* with them so that none of you get too overloaded with work to become a constraint to flow, then yes.
  
  References:
  
  1. [DevOps Values](https://itrevolution.com/the-three-ways-principles-underpinning-devops/)
  2. [YBI/YRI](https://devops.com/adding-accountability-you-build-you-run/)
  3. [What is DevOps](https://devops.com/introductiontodevops/)
  4. [Cross-Functional Teams and DevOps](https://puppet.com/blog/what%E2%80%99s-best-team-structure-for-devops-success)
  
  > **Comments:**
  > **username_0**: Thank you for those insights, especially pointing towards _increasing the flow of value_ which helps as a rule of thumb  
  > **username_1**: Or p-shaped. :)  
  > **username_2**: @username_1 I wonder how that would look :)  
  > **username_0**: I think pi-shaped is more appropriate :-D  
  > **username_2**: Hey, there's another `terminology` question you can ask - What's the appropriate shape to describe the skillsets required by a DevOps practitioner? :)  
  > **username_0**: A better question IMHO would be: What is the bare minimum of rights and privileges (e.g. root on a system, write access, ...) one needs to perform DevOps tasks  
  > **username_3**: @username_0, ah yes! π has two legs. Full Stack ;)  
  
  ---
  
  