Maturity doesn’t come with the passing of time, but with experience, whatever age you may start doing something. So it is with DevOps. In many ways IBM i teams have been ‘ahead of their time’, deploying small code increments to production fast and often. However we are seeing that requirements in integration and hybrid cloud are pushing the boundaries in DevOps transformation, and that to avoid costly, high-risk migration projects in the future it is important to act now and start taking further steps on that IBM i DevOps maturity journey.
Full DevOps maturity depends on sharing development methods and tools across all platforms to ensure easy collaboration between experienced developers and those new to IBM i. Yet for DevOps to succeed, a ‘hybrid’ way of working is needed, allowing access to the same tools from each team’s preferred interface and IDE. Of course, there is no one roadmap for DevOps maturity and each organization will prioritize different steps on the journey. With a progressive approach based on the use of industry-standard tools shared across the enterprise, each individual step will demonstrate a measurable ROI.