We’re launching the “Tap In Open Forum”: a new series of blog posts where we detail a current topic being discussed in the software development and testing community and invite you to participate in an open discussion with our best and brightest here at Skytap. Feel free to share your thoughts and we’ll do the same!
InformationWeek and IBM Mobile Technical Sales Leader Dustin Amrhein presented a webinar last week as part of their “DevOps Rado” series. The Frictionless Enterprise: Built for Business, looked at DevOps as a viable solution for removing the friction that prevents enterprises from innovating at not just the speed they would like, but at the speed absolutely required to stay relevant, and hopefully ahead of their competition.
Amrhein detailed how DevOps (no matter how you define it) is absolutely a major change for many larger organizations dealing with siloed teams, and that enterprises “need to be much more thoughtful and pragmatic in their approach” than smaller organizations. Amrhein suggested tacking the cultural changes required for a successful DevOps implementation first, and getting buy-in from senior level support before moving on to changing actual processes.
I got the chance to confirm the negative impact of an ongoing issue that many development and test teams face today, and have faced for many years. I asked Dustin about the role dev/test teams being forced to share on-premise resources played in creating harmful frictioned enterprises.
Dustin’s response confirmed something that we hear all the time from teams handicapped by this requirement:
Sharing on-premise resources results in fighting to carve up resources and being forced to share them across multiple teams. The solution of cloud resources is that they can be dedicated, and dev and test teams feel much less constrained. There’s no escaping the fact that shared on-prem resources do result in a frictioned enterprise.
We’d love to get your opinion on what you think causes the most friction/slowdown in enterprises today? Whether it’s an ongoing issue in your own organization, or maybe even a former problem you and your teams eradicated (congratulations!) we invite you to share your experiences or opinions in the comments section below.
Reps are standing by and we look forward to the discussion!