DevOps - Dont stop with Agile for developement

5 out of 10 customers that i have interacted in the last 30 days are talking about devops and interestingly everyone seems to go in that direction. In the Banking Organization context, "Run the org" and "Change the org" have been two accepted philosophy from getting things done. The line has blurred over the years. In a ideal world i would like to "run the org" with as much efficiency as possible and redeploy the energy in "change the org". In short time, this has changed a bit. From budgetary concern , we normally see the squeezing out of "run the org" portion of money and the change the org has taken preference and rightly so. While every school of thought has its own followings and haters, from the business perspective some of the points needs to be treated in the right spirit for success of the organization.

Run the Org: DevOps which normally is a cultural shift from the world of development and operation completely separated, advocates a close collaboration between both and overlap of responsibilities. A typical run the org kind of work would involve keeping the system going on, dirty fixes required to have the day to day operation going on. Some of the characteristic symptoms of "Run the Org" would be as follows

• Production support
• Data changes/errors including changes to database or file system.
• File exchanges or the failure of it.
• By passing some of programmatic error.
• Most importantly access to Production instances

If minutely considered there are different kind of activities involved and would mostly be done from ops perspective.

Change the organization advocates the need of more bang for bucks, faster, better. A DEVOPS philosophy would give rise to

• continuous release
• incremental features
• Continuous development.

So in essence, devops could be combined with a lot of competing and complementing philosophy to bring the best practice to the organization.