5 Steps to Continuous Delivery and APM Success
Solving the Continuous Delivery Mystery
November 06, 2012
Ashley Owen

Continuous delivery, continuous deployment and continuous integration — what do these all mean and are they the same thing, or even related? There is a lot of confusion around continuous delivery, but what isn't a mystery is that this topic and manner of releasing applications into production is a hot button issue in the industry right now.

Continuous delivery is defined as releasing into production high quality software quickly, through build, test and deployment automation. Basically the process allows organizations to release software into the “wild” in minutes, opposed to days or even weeks.

Test automation is the sticky point for many organizations opposed to continuous delivery — yes, we said opposed. Similar to how many IT organizations balked at adopting Agile development at first, organizations are doing the same for continuous delivery. The reason: it is a relatively new paradigm shift to traditional software deployment. The controversy: there is much less emphasis on the testing phase of the process than with more traditional software development and release.

What everyone can agree on is the driving force behind continuous delivery: the speed that software can be delivered into production is unmatched compared to traditional software release trains.

DevOps, Continuous Integration and Lean Computing

There are three aspects that make up continuous delivery: DevOps, continuous integration and lean computing – tying these together is when the magic happens.

The DevOps community focuses on infrastructure as code, monitoring and improved collaboration between the houses of development, test and operations.

Lean is about innovating efficiently, soliciting feedback from customers as quickly as possible and leveraging technical competences such as continuous integration, comprehensive configuration management, automation of build, test, provision and deploy processes.

Like any continuous improvement, it should be achieved incrementally, taking into account where folks are starting from and their ability to effect changes and adopt them. The tools, practices and patterns are now available to support this, and Serena uniquely orchestrates enterprise agility.

Incidentally the KPI or metric we should be measuring is the cycle time for the software delivery process (implies a continuous delivery workflow).

For continuous integration, there is a significant cost savings to consider. Since Continuous Integration is in the early development cycle, many changes are tested frequently with feedback immediately going the development team. Multiple changes from multiple developers are developed and tested with many deployments daily.

The earlier in the development, test and release cycle that a problem is identified and a fix developed, the lower the cost. It is much more expensive to fix problems after the application is in late-stage testing, pre-production, or production. Therefore, effective continuous integration reduces costs and reduces risks.

Today’s successful business is lean, efficient and lives online. It is an agile enterprise, relying on non-traditional IT imperatives such as Cloud, mobile and social computing. These companies are defined by the new and enhanced solutions empowering their IT stakeholders. From operating on mobile phones and tablets, to automating the release of their applications both on-premises and to the Cloud, agile enterprises live and breathe efficiency. Continuous deployment delivers the speed and agility these companies crave. They do not have time to wait for three-month development and release cycles they need software deployed in minutes.

While there is an interesting angle around APM and measuring performance, adoption, etc. once deployed as an ex development manager, there is still much improvement available in the area of test automation and in particular the adoption of TDD (Test Driven Development) practices.

We have come up with the five steps organizations can take to optimize continuous delivery:

Step 1: Make the release management process and workflow accessible for many different IT functions through a common function portal for: Business, Development, Test/QA, DevOps, Release, IT Operations and IT Service Management.

Step 2: Document detailed requirements in demand, stories and the requirements management process.

Step 3: Connect the requirements, development, and release processes. Ensure that the only changes that are released are those that have been defined by requirements management and approved by the business.

Step 4: Orchestrate the release management process with Development so that newly developed code from multiple development environments flows smoothly into the common release management process.

Step 5: Improve release management flexibility through improved support of:

- Traditional Stage-Gate QA methodology

- Modern Continuous Delivery QA methodology

- Support for many different environments for deployments (test, SIT, UAT, Staging, Pre-Prod, Production)

- Support for multiple platforms such as, Windows, Linux, Unix, Mainframe

For companies that want to take this developer-driven approach, there has to be an understanding of the changes required in getting to continuous delivery and how it affects the whole process for getting new software and updates out to the organization.  

The benefit of going down this route is that IT as a whole can be more nimble in responding to a changing market, whether this is launching new services or expanding available functionality. With a lot more businesses looking at how to expand the ethos of agile from development into their wider organization, this is a great opportunity to show the rest of the world how things can and should be done.

ABOUT Ashley Owen

Ashley (Ash) Owen is Serena Software’s Director of Orchestrated ALM Strategy for the ALM Business, providing product management assistance, field support and solution strategy & advice to our customers, prospects and partners. Extensive experience in the successful design and implementation of ALM solutions across Europe, APAC and America.



Ash has spent more than 23 years in Application Lifecycle Management and Software Change and Configuration Management markets. Ash has a singular focus on improving efficiency, automation and traceability within both Enterprise IT and Embedded Systems environments.

The Latest

July 01, 2015

CIOs are under pressure to support fast-evolving digital business scenarios but are finding traditional project and development methods unsuitable, according to Gartner, Inc. Enterprises are increasingly turning to agile development to speed up projects and illustrate their value ...

June 30, 2015

European organizations with the strongest Operational Intelligence capability are most likely to conquer the complexity of the fastest growing IT concerns, according to a new report titled Masters of Machines II, from analyst firm Quocirca ...

June 29, 2015

In a Catchpoint study from March, news sites were found to have a significantly higher percentage of their site content – as well as their speed bottlenecks – coming from third parties than sites from the eCommerce, banking, and travel industries. And in a more recent survey of the top 50 news sites across both desktop and mobile, it's easy to see why ...

June 26, 2015

While nearly half (45%) of service desks are interested in technology integration, 75% do not have the ability to calculate return on investment, according to new research by LANDESK in partnership with the Service Desk Institute (SDI) ...

June 25, 2015

ManageEngine recently released the findings of its inaugural ITSM survey of organizations using service desk software. The survey reveals the high level of first-time IT help desk adoption as well as the high number of IT help desk implementations beyond IT ...

June 24, 2015

Given the extent to which companies are contracting out their IT organization to other parties, outsourcing appears to be making a comeback. But migrating your IT infrastructure and management to the cloud or another party remains a hot topic. In the outsourcing procedure you lay down your criteria for the quality to be delivered by the other party. We have to do this, because otherwise the supplier will rest on his laurels, which is the last thing we want. So, we've got our criteria, but who's going to monitor them and how transparent are the figures? ...

June 23, 2015

For decades IT operations has been viewed as something of a back-office technology function; the IT engine room. That’s not wrong since the applications under control have generally been large monolithic systems of record designed to automate internal business processes. These systems have been inherently complex and tightly-coupled, so changing them has been difficult, time consuming and costly. As such, our operational mindset has remained firmly focused on maintaining reliability and avoiding risk at all costs – even if that means holding back releases and ticking off our colleagues in development. Not anymore ...

June 22, 2015

The "point of delivery", which is where users access composite apps, is the only perspective from which user experience should be evaluated. Thus, the most relevant metric for IT teams is not about infrastructure utilization. Instead, it is at what point of utilization the user experience begins to degrade. This means transaction completion. If transactions do not complete, user experience suffers as does business performance ...

June 19, 2015

When gathering performance data it is important to note that correlation does not prove causality ...

June 18, 2015

According to a new survey by Kaseya, 89 percent of IT groups in mid-sized companies are still in the early stages of IT management maturity and focus on day-to-day IT management tasks that are often time-consuming and manual. The remaining 11 percent have achieved higher levels of maturity and are reaping benefits in important ways for the business ...

Share this