Jump to content
DevOps is a movement to bring about collaboration between the members of development and operations groups. DevOps is community driven, and it has brought together many expert practitioners across the globe to work on best practices designed to help deliver value to customers faster.
Software development is constantly evolving and agile development methods have become increasingly popular. This is changing the way software is delivered. Gone are the days when a product has a couple of releases per year at most. And, this agile, iterative development can quickly overwhelm existing processes that support software development.
Companies like Flickr, which has releases on the scale of “10+ deploys per day,” along with companies that have transitioned to more frequent releases on a smaller scale, all have one thing in common: The number of releases coming to operations from the development side of the house has put significant strains on both QA and operations staff. Removing obstacles without sacrificing quality or control by working closely together is a part of the solution to quickly deliver value to customers.
DevOps initiatives can help avoid the chaos that can occur with rapid development cycles. Instead of having to break down silos over and over again, DevOps enables an orchestrated flow from business to development to operations.
Some DevOps benefits reported by Serena customers include:
“We have increased quality and driven down deployment time by 50%.”
“We have decreased the amount of manual work it takes to create a release and deploy it by ~90%.”
“We have standardized and automated our end-to-end coding and release process to reduce human errors.”
Part of creating an environment where DevOps can be successful is having a process that works equally well for both development and operations. Serena’s release management technology can provide a layer of abstraction that allows Dev and Ops to share the same process but work in their own way. Add in some dashboards and there is visibility into the processes and releases, no matter if you are a practitioner, a manager, or an executive.
In order to keep releases flowing, release automation is key. At Serena, we can provide first-class deployment automation technology, sophisticated release pipeline management, and self-service environment provisioning. Our solutions can also integrate with your existing continuous integration and testing solutions to help you get even greater benefit.
By managing your processes and automation and integrating with your existing tools, you can innovate quickly and still maintain visibility, reliability, and control.
Agile Development – Agile development is a lightweight framework that aims to deliver value to customers faster by developing software in short iterations.
Change Control Board – This is the committee that assesses change requests and decides whether to accept or reject a request.
Change Management – As the process responsible for controlling the lifecycle of all changes, the primary objective of change management is to enable beneficial changes to be made, with minimum disruption to IT services.
Change & Release Management – Change and Release Management represents a process-based approach that brings development and operations teams together to capture, triage, and prioritize change requests, route them to the right individuals for fulfillment, speed the deployment of these changes into production, and then notify business counterparts of the status of their requests.
Continuous Integration – This describes the process of building source code every time code is committed to a source code repository.
Continuous Testing – Continuous Testing builds on Continuous Integration and Test Driven Development to ensure that your code is always tested when changed, shortening the time it takes to find software defects.
Continuous Deployment – This is the practice of automatically building, deploying, and testing software in an automated manner without human interaction. Software is deployed and tested in environments along the path to production assuming that criteria are met, allowing a release to move from one environment to another. Continuous Deployment does not include automatically deploying to production without human sign-off.
Definitive Media Library (DML) – DML is a location in which definitive, approved versions of software configuration items are stored.
DevOps – DevOps describes a movement by development and operations practitioners to break down silos between teams in order to bring value to customers faster.
Infrastructure as Code – Infrastructure as code is the practice of defining all of your infrastructure provisioning as scripts, which are then stored in source control just as any other code would be.
Path to Production – The path to production is how a request for a change moves from the initial request to production environments.
Release Vault – See Definitive Media Library
Revenue Apps – Revenue applications (RevApps) are an organization’s software applications that directly touch customers and/or bring in revenue. They are critical due to their impact on revenue, reputation, and customer engagement. The speed with which RevApps get enhanced directly correlates with how quickly the organization can respond to customer requests and changing market conditions.