Demystifying “Ops”

“Ops Gone Wild” … Do you ever pause to wonder why does every tech function now have an Ops suffix? What is the intuition behind the Ops movement? Most importantly, what/where is the value? So I decided to do a bit of my own digging and this is what you need to know –

• Any function with an Ops in the end in simple terms represents “the set of practices that works to automate and integrate the processes between 2 (or more) functional team members”.
• The intent is to move away from the “my department / your department” mindset to the “one team” mindset.
• So if you are looking at #devops , you are looking at the development flow from requirements all the way to release and maintenance.
• If you are looking at #itops , it is the set of processes used by the IT team members, from acquiring to configuring and maintenance.
• The addition of the “#automation” and “#integration” elements into the traditional process flows is really the game-changer here that elevates it from a legacy construct to an agile construct.

  Most importantly, all of these are derived from the #agile methodology which promotes adaptive planning, continuous delivery, and continuous learning while delivering small units that are consumable and incremental, so that the teams can respond to change swiftly. I hope next time you run into another Ops variant, you will “take it stride”. #mlops #devsecops #softwaredevelopment #technologymanagement #productmanagement #govcon #govtech