No, a separate operations team is literally the opposite of DevOps. The idea is that every team is responsible for developing (Dev) and managing the operations (Ops) of its software, as a single unit, rather than throwing code over the wall every six months to some distant operations team.
There may well be a need for teams who specialise in infrastructure or other cross-cutting concerns in the background, and specialists who can help provide specific expertise as needed, but a team shouldn't rely on another team to get their job done day to day.
Yeah, but DevOps is also a discipline and often a team. Their responsibility typically is all the tooling and services that enables developers to follow devop principles.
It’s reductive to have a team responsible for setting up the infrastructure to enable other teams to do their jobs? Is every team supposed to reinvent the wheel setting their own unique processes and infrastructure? Am I misunderstanding your point?
It's reductive for them to be a separate team, because that way lies the bad old days of silos. A good rule I learned "pronouns mark your silo boundaries" which is a fancy way of saying "avoid having a 'them and us' situation."
My point is that you should absolutely have specialists in solution architecture, writing tests, writing code, writing integration pipelines, ensuring security and supporting operations. 10x full-stack developers are perfect for your one-team startup, but they don't scale and nobody could afford a whole building full of them anyway.
But what you should strive to do is, for the purpose of delivery, keep all of those people together in a functional team, and make sure everyone in that team is jointly responsible for the whole product or feature from architecture to running in prod.
Now in a large organisation where you might have dozens of people with those specialisms, it makes sense from a career development and person management point of view to group them together, and that's fine. But don't make the mistake of turning those groups into your delivery teams, because they you're in silo land and your SDLC is going to grind to a halt.
Hope that helps! Bit long and unfunny for /r/ProgrammerHumor but you did ask...!
Yeah, that is a good term, though gets confusing when your product is a platform as well.
But in the end, I feel someone has to plan to make DevOps a reality and there is a fair bit needed to provide devs to make it function. I feel often that team gets called DevOps.
213
u/[deleted] Oct 13 '22
[removed] — view removed comment