DevOps benefits for ODI (lessons learned)

When people make a decision to invest in software it is fairly easy to talk about benefits. Especially the intangibles ones. But what about the tangible benefits?

And this for an end-to-end Life Cycle Management solution for ODI.

When looking at the tangible benefits, we believe you should have a look on the impact for each involved stakeholder. Stakeholders are not just developers, but also the quality assurance people, operations and the final users, our clients. Not to forget the architects.

Each of them will have a different look and feel about the tangible (and intangible) benefits. And each category of stakeholders can be looked at from a narrow or broad perspective. When you talk about developers, do your DBA’s also play a role? Should their work also be taken into account?

Next key element is the Life Cycle process your architects develop that you will follow: What are the different phases? Just the classic DTAP (Development, Test , Acceptance and Production)? Or larger? What about release management? What is the versioning strategy?

What must be managed: just the source code or also database scripts, automated test runs, documentation and so one? Last but not least what tooling is used during that process? Of course ODI Studio is key, but will you also use automating testing tools or data modeling tools,..?

Once you have figured that out you can see which of the following tangible benefits you can or will reached and this from the perspective of each stakeholder by implementing DEVOPS for ODI.

Some tangible benefits:

  • Decrease in development cost
  • Decrease in quality assurance cost
  • Decrease in operations cost
  • Shorter Development Cycle
  • Shorter QA Cycle
  • Shorter Deploy Cycle
  • Increased Release Velocity
  • Improved (faster) Defect Detection
  • Improved (faster) Defect Resolution
  • Reduced Deployment Failures and Rollbacks
  • Reduced Time to Recover upon Failure
  • Faster time to market

Our LCM solution for ODI allows you to follow exactly the process your architects designed, takes into account the tools you are using and streamlines the communication and collaboration for all stakeholders.

Picture of Rene De Vleeschauwer

About the author

Hello, my name is René De Vleeschauwer.

Throughout my career I've been responsible for the development of enterprise software. Since 12 years I've been leading the development of IKAN ALM, an open DevOps framework.

Do you have any questions about this post? Just ask me!

Get free insight!

Let's analyze your current development and release process, and show you how to make it much faster and 100% reliable.

Yes, I want insight

Do you want to recieve the latest news and updates?