Do I have to jump into the DevOps water with both feet?
Comments (7) Visits (10108)
With all the hype and promotion DevOps is getting in the marketplace, one may ask the question: Is it necessary to implement the entire DevOps solution stack to see the benefits? As a manager within IBM Systems and Technology Group (STG) who is responsible for the implementation of continuous delivery for thousands of developers, I would answer the question with a resounding no.
If an organization attempts to implement the entire DevOps solution stack, not only could there be a lack of overall vision and focus, but the resources required might not be available. What would I suggest?
Find an area of focus that gives your organization a large return on investment while positioning your strategy for the future implementation of additional DevOps solutions.
For an organization like STG, the initial foray into DevOps came with IBM
What was once a silo of processes and tools for each product line within STG is now a very efficient and streamlined delivery process that crosses product boundaries. With our first foot wet in the DevOps water, we can now expand into other areas of optimization:
Each organization is going to have a different story. You may be working with open source and require a lightweight Source Code Manager (SCM) but need the IBM SmartCloud and IBM UrbanCode capabilities. You may be like us in STG and determine that starting with an enterprise-level SCM like RTC focusing on plan and change management is the first step. In either case, create a vision, map the strategy and keep the focus.
Based on my experience, you don’t have to jump into the deep end with both feet right away! How is your organization getting wet with DevOps? Which solution(s) are you adopting first and why?