First things first

This blog series is articulated about the things that are involved in DevOps. This could be beneficial for anyone working in the IT space[Developer, Infra support Engineer, Data Scientist(yes, you read it right), Test Automation Engineer, Engineering Manager, Product Owner/Analyst, Cybersecurity Specialist, Network Support Specialist, etc.,]whereas. the more tech aspects in the future blogs would be suited more for DevOps geeks. If you’d like to get benefitted from a weekly post, please follow me 🙂 thanks.

Let’s dive in

What is DevOps?

DevOps, a culture that ties up the knots and acts as a bridge between Development and Operations which were in silos a few years ago.

To give you a background from my experience, I was working for a banking client as an Application support Engineer where I wasn’t having any visibility about either the application code or Developer’s day to day responsibilities. I was working to support the users who overcome the issues on their applications once we complete the deployment of the war/jar files that were provided by a build package management team. We would take care of the infrastructure implementation required for the applications with the assistance from Application Architect. If an issue arises, we had a mindset ready to throw at the application team on the way code were written or built, and the Application team would throw issues at us saying it was an infrastructure issue. There was no end game, but the blame game!

Application developers would be working on their deadline to finish a project[Yeah, Waterfall methodology] and application support/admins would be working on their deadlines to set up an application and troubleshoot customer issues.

Since there was no iteration process involved, there was no sync between these teams after initial development plan, in case of any change in the initial requirements.

As you could see, a lot of barriers between them, but at the end of the day, they deliver value to customers. In recent days, as an end-user, we want websites/mobile apps to have frequent updates to apps in terms of new look, enhancements, bug-fix, patching, fixing vulnerabilities to be safe and stable, and the best user experience. Imagine the team set up as above to bring in new releases/enhancements/new-look to us as an end-user which takes months to deliver and does not have a competitive advantage, does not have fixes for security immediately, not sure about rest of the world but I won’t be using that app, Of-course! This is where the DevOps approach/culture would serve it’s rightful place.

How DevOps is beneficial in today’s world and the foreseeable future?

DevOps gives loads of benefits to all people who strive to have a wonderful useful website/app.

As you can see from the image, it benefits everyone involved in the Application Development Lifecycle. It will accelerate the release, keeps everyone in the phase competitive for a better product that will benefit the customers. It makes everyone visualize their part in the application development, adoption, and feedback/continuous improvement journey.

How is it happening? What is required to make it happen?

As DevOps has a lot to offer, it takes a lot to make it happen. First and foremost is the mindset of anyone as part of the DevOps approach.

I know that the words in the picture are basics but embedding these in our mindset to do everyday work is challenging and interesting. Everyone in the team involved from building to shipping a product should embrace these key characteristics. Trust me, This will make you a better person personally. Please read the words out loud from the above picture to have your mindset aligned 🙂 before we dive into tools in the DevOps space!

What are the skills and tools required in a DevOps team?

As automation and continuous improvement as a core principle, we could leverage any tools that enables us to achieve the culture we strive to build a product/app.

If we need to start from scratch, we would need things in this order to develop a product[At least a few from this :)]

Source :