OpsDev - The new TRUTH of Agile Development

Someone very close to my heart always reminded me - "change is the only constant"! How true! Ironically, we work in an industry - where SDLC from inception had all the good practices embedded in it, and yet, we took the liberty of gradually letting them slip through. And then in 2001 - when some smart people got together to remind us of the 4 themes and 12 principles of Agile, we took it as a new path of salvation. Doesn't that point to the fact - we need change, we embrace change and we in fact love change (perhaps unconsciously)!

With the change in motion - you must have come across the buzz word of DevOps. And yes - as you have worked on it, you may already have experienced, that there are more definitions of DevOps, than real practitioners available. But does DevOps really mean a bridging act across Development and Operations? Assume you are driving an Enterprise IT with hundreds of vms (or docker - if that serves you) spinning around you. And your development team is churning out new applications or patches almost daily (or even hourly). Do you see there is time for Developers and Operations collaborating? Nonsense! It has to be flowing in the vein - in the practice! Things should be moving like a factory - where we pull items from supply line & ensure that "queues" are only found in dictionary.

Theoretically - sounds fascinating! Practically - you need to have OpsDev to drive this. How OpsDev? Why not DevOps? What's the big deal about tweaking the name?

Think about it! Do you see your Developer pulling in an Ops person while his/her code it's getting built? Or is it more practical for Ops team to have a developer coming and explaining the war file content, it's use case, its possible touch points and securities - so that Ops knows how to place and build it (after all, ensuring stability, security, integrity is a major concern for them)? Make this practice a routine, embed this in your team and you are doing it day-in day-out, even before you realize that your are following OpsDev (or DevOps - whatever name suits you)!

After all, what's in a name? :)

I get scared looking at the ever growing dominance of Methodology oriented frameworks - which claim to provide a solution to every problem & yet - they themselves may end up creating more than solving any (if not done correctly). Are those SAFe? It is very difficult to single one out - no one is LeSS! But my humble request will be - whatever you do, let your common sense and experience drive the decisions for you (& not any ambiguous methodology).

Wish to share it? Use this: http://bit.ly/1LnBX1K