As @raphabot suggested – I have some opinions in this space
First, DevOps has become a buzzword in recent(ish) years. There are so many organizations that are like “what day will we have the DevOps”. The answer is you wont. If you’re looking for a day that you’ll have it – you’re simply looking for the wrong thing or not asking the right question. DevOps is not something you have. It’s in the everyday actions and decisions you make as an organization.
Now… Those decisions that I mentioned. So many organizations are cutting ops, telling devs “do everything” and “use whatever tool you want” because innovation or #MoveFastBreakThings but that’s not it either. In order to really harness the power of DevOps organizations need to act as enablers of thought leadership (another buzzword). Ops has incredible and deep system knowledge that will help you drive the innovation you want and developers have the ability to drive your organization forward through innovative applications that ultimately drive customer experience. The whole point is marrying the two groups and their collective wisdom and harnessing that power. Do that.
@madelinev also brought up a great point. You can’t have just a team in an organization “doing DevOps”. I understand why some organizations have titled roles as “DevOps Engineer” or teams as “DevOps Teams” – because like I said it’s a buzzword. It’s a means to attract fresh ideas/talent while also trying to meet market demand and sometimes (not always) navigate some corporate red tape. But there needs to be an understanding that DevOps is an entire organization cultural awakening.
Practices. Those have to change. Throwing things over the wall at each other. That has to change. No amount of organizational change management is going to help achieve more harmonious DevOps practices that help drive the business value that organizations crave if behaviors like that continue. In order to achieve this “thought leadership” ideal state your teams need to be empowered to collaborate - and not just empowered, but encouraged. Your teams need to feel like they have the space to do this. If there’s still corporate red tape in the way keeping them from collaborating or having ownership in driving the organization forward give them the space and power to remove those blockers.
Speaking of red tape - remove your silos, don’t create new ones. If you have an organizational structure that is siloed, your organization is going to have to knock those walls down.
Then finally - practice what you’re preaching. As an organization, if you have done these things and knocked down walls and given people space to do things remember not to drive people back to the behaviors you’re trying to change. Praise collaboration. Empower it. Praise thought leadership. Don’t dictate.
I’m realizing that even though I said “finally”, I have tons more to say.