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 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.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Cecily
1 days agoValentin
7 days agoBarrett
8 days agoValentine
11 days ago