Which or the following commonly adoptee DevOps team approaches is the BEST example of a DevOps teaming model that does not fully support the overall goals of DevOps?
A stream-aligned team? Sounds like a bunch of surfers trying to ride the DevOps wave. I'll stick with the good old-fashioned site reliability team, at least they have a solid foundation.
Honestly, the DevOps as a tools team sounds like a recipe for disaster. That's like having a team of mechanics trying to tell the drivers how to drive. Not a good look.
Hmm, a site reliability team? Isn't that just fancy IT operations in a new suit? I'll have to go with the tools team on this one, it's the most isolated from the actual DevOps principles.
A DevOps advocacy team? Sounds like a bunch of cheerleaders trying to sell the DevOps dream. I'll go with C, a stream-aligned team, as the best option here.
I think the DevOps as a tools team is the least supportive of the overall DevOps goals. Doesn't really foster the collaboration and shared responsibility we're going for.
Fannie
8 days agoCarma
10 days agoMargarita
14 days agoXuan
15 days agoXochitl
21 days agoNina
21 days agoMargarita
27 days agoLeota
29 days agoIndia
13 days agoJesus
14 days agoCasandra
21 days ago