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?
I'd have to say the DevOps as a tools team is the worst option. It's like trying to build a house with a toolbox but no actual construction workers. Talk about a 'tool'ish approach!
The site reliability team? Sounds like they're more focused on keeping the lights on than actually improving the development and deployment process. Might as well call them the 'DevOps Killjoys'.
A stream-aligned team sounds like the way to go. It promotes that whole 'you build it, you run it' philosophy that's central to DevOps. Plus, it's a lot less boring than being on the 'DevOps Tool Police' team.
I'm going with option B - the DevOps advocacy team. They're more focused on evangelizing DevOps than actually implementing the practices. That's not going to get the job done.
The DevOps as a tools team approach doesn't really align with the overall goals of DevOps. It's too siloed and doesn't promote the collaboration and cross-functional mindset that DevOps is all about.
Malissa
20 days agoBeckie
9 days agoPearline
10 days agoWinfred
11 days agoBarrett
25 days agoWillard
28 days agoStephane
1 months agoJoana
2 days agoTijuana
6 days agoJarvis
14 days agoCecily
1 months agoValentin
1 months agoArt
12 days agoAmalia
16 days agoDaniel
20 days agoAlaine
25 days agoBarrett
1 months agoValentine
2 months agoDoyle
11 days agoClaudia
13 days agoAndrew
15 days ago