Welcome!

Microservices Expo Authors: Elizabeth White, Gopala Krishna Behara, Sridhar Chalasani, Tirumala Khandrika, Kelly Burford

Related Topics: Microservices Expo, Java IoT, Microsoft Cloud, Linux Containers, Containers Expo Blog, SDN Journal

Microservices Expo: Article

Does Continuous Deployment Mean Continuous Disappointment for Customers?

The “delivery” or “deployment” in continuous delivery doesn’t necessarily imply delivery to the end customer.

By Dhruv Gupta, Director of Product Marketing at Perforce

This article was originally published on the Perforce Blog.

An interesting article came out recently, “Why Continuous Deployment may mean Continuous Disappointment for your Customers.” It correctly identifies the human need for a shiny, new thing every so often. And it argues that the practice of continuous deployment could lead to disenchantment with incremental updates.

The article cites examples of companies whose customers were left disillusioned by incremental additions or subtractions to existing capability.

There are at least a couple of underlying issues to explore.

  • What does it mean to continuously deliver? What are we delivering, to whom, and when?
  • What are my customer’s expectations? Are they being met?

First, it is important to understand that the “delivery” or “deployment” in continuous delivery doesn’t necessarily imply delivery to the end customer. The bible on the subject, “Continuous Delivery” by Jez Humble and David Farley, suggests that continuous delivery simply implies maintaining a state of readiness. The state of readiness implies you did deliver an update to someone. It did go through quality control and stakeholder approvals. However, business gets to decide the what, the whom and the when. This works really well for verticals like cloud-based software, where you might want to deliver new functionality to a select group of customers to begin with, vet that functionality, and then roll out to a larger audience. Continuous delivery doesn’t necessitate delivery of every update to the customer, the moment the code is deployed. In fact, you might deliver daily updates to only your product manager and QA team, and that is it. This distinction is subtle, but often overlooked, leading to confusion.

Second, most business-minded staff would agree that to grow brand appeal it helps to have big announcements at a regular cadence. Depending on the sector, the announcement could be yearly, or quarterly if you just have a primary product line, or at a higher frequency across several product lines. We have seen the likes of Apple announce a new phone, a new device, the one more thing, at least once a year. It builds a sense of mystique and excitement. People wouldn’t wait in lines for a new version of a phone released every month. Building anticipation is essential if you want people to sit up and take notice. In other sectors, a constant stream of updates is more desirable. We see this phenomenon with mobile apps. No big announcements required — just updates. We are used to that. Major updates still come every so often.

This also brings to bear an important issue. Customers don’t like big changes frequently. It takes time for us to get used to a new product. Some products come only at a considerable cost. A new update that arrives sooner than justified by the cost of acquisition can create a backlash. Release a new product too quickly on the heels of the last one—without advance notice—and you might cause angst in the customers who only recently bought the previous version. Loyal customers might feel burnt by the quick update. They might even abandon the brand altogether as a result of feeling the company is apathetic to them. This is especially the case with hardware products—cameras, computers and the like.

If practiced the right way, Continuous Delivery should allow marketers to balance the extremes. You can choose to release incremental updates as they become available to all customers. You can choose to limit major updates or new deliverables until you’re convinced that they satisfy customer requirements, and go for the big launch. Either way, continuous delivery can help return control to the business.

That said, there is much to learn about the impact of Continuous Delivery on a business and its customers. With customers in many different verticals, we have a great vantage point to see how this practice evolves. Our data suggests there’s a lot of movement to this practice. And we’re excited to play an important role in the shift.

To learn more about Continuous Delivery, have a look at our CD Report.

About the Author

dgupta's picture

Dhruv Gupta is the Director of Product Marketing at Perforce Software. See all posts by Dhruv Gupta

Explore Trends in Continuous Delivery at SDLC Acceleration Summit

Want to explore Continuous Delivery trends and best practices along with your peers and industry experts? Join us on May 13 in San Francisco for the SDLC Acceleration Summit.

sdlc_banner_continuous
The summit is designed to help industry leaders address the growing concerns about accelerating software delivery without compromising application quality. This vendor-agnostic summit will explore topics such as:

  • The Future of the SDLC
  • Integrity within the Software Supply Chain
  • Reassessing the True Cost of Software Quality
  • Gaining a Competitive Advantage via an Advanced Software Delivery Process

To kick off this event, Theresa Lanowitz, software industry expert and founder of voke, inc., will be delivering the keynote.

More Stories By Cynthia Dunlop

Cynthia Dunlop, Lead Content Strategist/Writer at Tricentis, writes about software testing and the SDLC—specializing in continuous testing, functional/API testing, DevOps, Agile, and service virtualization. She has written articles for publications including SD Times, Stickyminds, InfoQ, ComputerWorld, IEEE Computer, and Dr. Dobb's Journal. She also co-authored and ghostwritten several books on software development and testing for Wiley and Wiley-IEEE Press. Dunlop holds a BA from UCLA and an MA from Washington State University.

@MicroservicesExpo Stories
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone in...
Many IT organizations have come to learn that leveraging cloud infrastructure is not just unavoidable, it’s one of the most effective paths for IT organizations to become more responsive to business needs. Yet with the cloud comes new challenges, including minimizing downtime, decreasing the cost of operations, and preventing employee burnout to name a few. As companies migrate their processes and procedures to their new reality of a cloud-based infrastructure, an incident management solution...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
Gaining visibility in today’s sprawling cloud infrastructure is complex and laborious, involving drilling down into tools offered by various cloud services providers. Enterprise IT organizations need smarter and effective tools at their disposal in order to address this pertinent problem. Gaining a 360 - degree view of the cloud costs requires collection and analysis of the cost data across all cloud infrastructures used inside an enterprise.
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
Our work, both with clients and with tools, has lead us to wonder how it is that organizations are handling compliance issues in the cloud. The big cloud vendors offer compliance for their infrastructure, but the shared responsibility model requires that you take certain steps to meet compliance requirements. Which lead us to start poking around a little more. We wanted to get a picture of what was available, and how it was being used. There is a lot of fluidity in this space, as in all things ...
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
The notion of improving operational efficiency is conspicuously absent from the healthcare debate - neither Obamacare nor the newly proposed GOP plan discusses the impact that a step-function improvement in efficiency could have on access to healthcare (through more capacity), quality of healthcare services (through reduced wait times for patients) or cost (through better utilization of scarce, expensive assets).
Admiral Calcote - also known as Lee Calcote (@lcalcote) or the Ginger Geek to his friends - gave a presentation entitled Characterizing and Contrasting Container Orchestrators at the 2016 All Day DevOps conference. Okay, he isn't really an admiral - nor does anyone call him that - but he used the title admiral to describe what container orchestrators do, relating it to an admiral directing a fleet of container ships. You could also say that they are like the conductor of an orchestra, directing...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
Recent survey done across top 500 fortune companies shows almost 70% of the CIO have either heard about IAC from their infrastructure head or they are on their way to implement IAC. Yet if you look under the hood while some level of automation has been done, most of the infrastructure is still managed in much tradition/legacy way. So, what is Infrastructure as Code? how do you determine if your IT infrastructure is truly automated?
Every few years, a disruptive force comes along that prompts us to reframe our understanding of what something means, or how it works. For years, the notion of what a computer is and how you make one went pretty much unchallenged. Then virtualization came along, followed by cloud computing, and most recently containers. Suddenly the old rules no longer seemed to apply, or at least they didn’t always apply. These disruptors made us reconsider our IT worldview.