Isolated “Silos”
Development is under pressure to develop new features and applications to meet business objectives. Everything “works well” in their environment. However there is a risk that a new software release is “tossed over the wall” to Operations. Here new releases are prepared for deployment. Operations start to develop scripts and prepare configuration files to reflect the production environment (which is typically different to the development environment). This can lead to delay, errors and rework.
Often the larger silos aren't in the same office, the same city, or sometimes not even in the same country.
DevOps enhances communications and collaboration across departments. DevOps promotes a fast and responsive, yet stable, operations environment that is synchronized to the development innovation process.
Need for Speed
Software development has used a sequential approach where specifications drive development that drive roll-out. Agile development was introduced to shorten the long development cycles associated with sequential development. Agile methodology uses sprint cycles (i.e. a 2 week development cycle) to produce small incremental product enhancements. However aggressive release dates created additional stress and were hard to meet so software was released before it was ready. This put more pressure on IT operations to support this software.
DevOps provides a methodology for both developers and IT operations personnel to achieve rapid software releases with full testing and robust roll-out.
Disparate Technology and Tooling
There is often a mismatch in development and operations tooling. Software developers typically use one set of tools, and systems administrators another. Common tools are scarce, e.g. bug trackers and SCM. The challenge is adopting a common set of tools and driving consistency in integration and deployment.
DevOps drives a unifying environment for tooling, change management and process monitoring.
Need for Multi Disciplinary Experts and Resources
Typically a project team consists of business analysts, developers, QA specialists, testers, DBA’s, release managers, system administrators, and many more.
DevOps encourages participants to work cross-functionally and derive benefits from a collaborative approach leveraging a broader skill-set.
Development is under pressure to develop new features and applications to meet business objectives. Everything “works well” in their environment. However there is a risk that a new software release is “tossed over the wall” to Operations. Here new releases are prepared for deployment. Operations start to develop scripts and prepare configuration files to reflect the production environment (which is typically different to the development environment). This can lead to delay, errors and rework.
Often the larger silos aren't in the same office, the same city, or sometimes not even in the same country.
DevOps enhances communications and collaboration across departments. DevOps promotes a fast and responsive, yet stable, operations environment that is synchronized to the development innovation process.
Need for Speed
Software development has used a sequential approach where specifications drive development that drive roll-out. Agile development was introduced to shorten the long development cycles associated with sequential development. Agile methodology uses sprint cycles (i.e. a 2 week development cycle) to produce small incremental product enhancements. However aggressive release dates created additional stress and were hard to meet so software was released before it was ready. This put more pressure on IT operations to support this software.
DevOps provides a methodology for both developers and IT operations personnel to achieve rapid software releases with full testing and robust roll-out.
Disparate Technology and Tooling
There is often a mismatch in development and operations tooling. Software developers typically use one set of tools, and systems administrators another. Common tools are scarce, e.g. bug trackers and SCM. The challenge is adopting a common set of tools and driving consistency in integration and deployment.
DevOps drives a unifying environment for tooling, change management and process monitoring.
Need for Multi Disciplinary Experts and Resources
Typically a project team consists of business analysts, developers, QA specialists, testers, DBA’s, release managers, system administrators, and many more.
DevOps encourages participants to work cross-functionally and derive benefits from a collaborative approach leveraging a broader skill-set.
