One team with one goal. That phrase summarizes DevOps’ ultimate purpose. With DevOps, teams are not siloed, because development and operations work together. They push the project forward and are mutually invested in its success. Developers no longer throw an installation DVD and printed instructions “over the wall” to the operations team and expect a successful release. Development and operations staff are joined at the hip from start to finish, ensuring a continuous stream of successful releases.
An organizational chart for DevOps may still depict separate development and operations teams in some cases. That often depends on the unique needs of a business; however, tight alignment and integration of development and operations staff is critical and the cornerstone of a successful DevOps-based organization. A DevOps strategy must have consistent goals and be based on the value delivered to the business. Staff may be matrixed together by products or platforms or simply integrated through strong collaboration, integrated processes and consistent metrics for success.
But culturally under the DevOps approach, skillsets, mindsets, collaboration, tools, processes and focus shift and take a broader approach. Developers must understand the environments in which they are deploying. Operations must be part of the entire release pipeline, ensuring data and environments are consistent and support the needs of the applications. Developers and operations staff will work side by side when bugs are found or issues are encountered in production. End-to-end visibility is provided for a product and supporting teams starting with unit level development through build, QA, release and ongoing maintenance. Development sees and is invested in the production success, and operations sees and is invested in high quality development.
This is not a development or operations question. This is organizational-wide change for creating greater business value.