|By Jackie Kahle||
|December 11, 2014 11:00 AM EST||
Four Best Practices for DevOps Success
Much of what is written about DevOps focuses on the development team and on making things faster. And the ops team is thinking, "Whoa, slow down! We need to ensure there's quality, so going fast with poor quality doesn't help." So dev and ops are immediately at odds with each other, because their goals are different.
You want to center all teams around the common objective of having a predictable and reliable customer experience. That's just not a coding issue. There is a difference between quality of code and quality of experience, and what really matters to an organization is quality of experience. Dev, ops, and testing all succeed together in creating a quality experience, or they fail together.
Achieving DevOps success requires coordination across different IT department workflows, and poses a challenge for many organizations. Success ultimately depends on an IT organization's ability to integrate technologies and processes at key points along individual departmental life cycles. The goal is to maintain the same levels of control while moving more quickly through the processes.
A recent Gartner report, Best Practices to Sync and Streamline DevOps Cycles for Faster IT Service Delivery, by Cameron Haight, Jim Duggan, and Thomas Murphy, published April 12, 2013 offers four best practices for enterprise end users to further interdepartmental collaboration:
- Update departmental cycles to reflect the new requirements for velocity-oriented IT organizations.
- Coordinate cycles across departments to reduce process and workflow delays and information loss.
- Identify convergence areas that require multidepartment collaboration and technology integration.
- Perform continuous improvement of workflows to reduce waste and improve IT effectiveness.
To learn more details about these practices and how you can streamline your DevOps cycles for faster IT service delivery, I encourage you to read the full Gartner report, which is available compliments of CA Technologies.
The basic integration architecture, as defined by ESBs, hasn’t changed for more than a decade. Most cloud integration providers still rely on an ESB architecture and their proprietary connectors. As a result, enterprise integration projects suffer from constraints of availability and reliability of these connectors that are not re-usable across other integration vendors. However, the rapid adoption of APIs and almost ubiquitous availability of APIs amongst most SaaS and Cloud applications are ra...
Jul. 2, 2015 03:18 PM EDT Reads: 156
Jul. 2, 2015 03:00 PM EDT Reads: 951
Jul. 2, 2015 02:52 PM EDT Reads: 204
Jul. 2, 2015 02:30 PM EDT Reads: 1,140
Jul. 2, 2015 02:15 PM EDT Reads: 726
Jul. 2, 2015 02:15 PM EDT Reads: 2,181
Jul. 2, 2015 02:00 PM EDT Reads: 1,021
Jul. 2, 2015 01:45 PM EDT Reads: 2,271
Jul. 2, 2015 01:36 PM EDT Reads: 401
Jul. 2, 2015 01:00 PM EDT Reads: 1,203
Jul. 2, 2015 01:00 PM EDT Reads: 1,032
Jul. 2, 2015 12:00 PM EDT Reads: 2,012
Jul. 2, 2015 11:50 AM EDT Reads: 413
Jul. 2, 2015 11:17 AM EDT Reads: 410
Jul. 2, 2015 11:15 AM EDT Reads: 1,030