For me DEVOPS is the combination of a lot of best practices of different IT domains such as Agile principles, Application Lifecycle Management processes.
There is no “one fits all” solution to be implemented and it’s really dependent on the organization. The end goal of DEVOPS is to reduce “time to market”
and improve the quality of the released product.
There are, of course, always quick wins every organization should have that might have to be put in place and the best option is to identify what is going
on in the organization right now.
Many companies start with buying and implementing new tools in order to get their performance improvements but often this doesn’t end well for several
reasons. In most cases tools introduce standard processes and, with a default implementation or supported by a vendor consultant, the new processes will
not be aligned with the procedures and processes of your organization. This will lead to frustration in the end-user community and the result will be an
even worse performance.
A much better approach is to first document the value-stream map for your product. The value-stream map tells you the story of your product (or a feature)
lifecycle from conception till release in production.
Based on my experience, two main tracks are really key in a DEVOPS program: