DevOps has been around for years. One could start a crusade based off of some of the arguments I’ve heard surrounding this topic and the minutia about what it really means. The reality is that everyone is right depending on their point of view, stake in a project and maturity level of the organization.
DevOps is a culture that organizations need to achieve the market pace and be ahead of their competitors. How that is realized within an organization is where the confusion comes in because DevOps never really ends. Unlike major software upgrades of the past with a clear beginning and end, a DevOps environment is a constant cycle of incremental updates, testing, and continuous monitoring and feedback, which then flows back into additional requirements and user stories.
Ultimately, whether you’re a devOps engineer, devOps manager, or a devOps Champion, the goals remain the same:
- Service delivery is continuous
- Reduces complexity in the pipeline
- Manpower is reduced.
- Better collaboration of delivery teams
- High rate of features delivery
- Stability of live environments.
- Enabling faster feature time to market.
- Competitive advantage.
How each company chooses to realize these benefits and promote the devOps culture is going to depend upon the company itself. But just like the agile framework that devOps is based on, it is results and the delivery of a working process that matters the most.