A Holiday Tradition: 2017 Continuous Delivery Predictions

It’s that time of year. As the calendar year comes to a close, many of us are following time-honored traditions: making preparations for the holidays, planning some much-deserved time off and enjoying time with friends and family.

In the business world, the year-end also brings its own traditions, and first among those is making predictions for the coming year. I’m not one to forgo traditions, so in this article I’ll share my thoughts on the upcoming year within the context of the continuous delivery movement.


To level set, continuous delivery is the most evolved and modern state of software development and testing—and is core to a successful DevOps strategy. Organizations that are able to achieve continuous delivery can rapidly develop, test and release applications—with higher quality and at lower costs.

Simply put, the ability to more continuously deliver software is one of the biggest advantages to attain in the application economy, where the battleground for consumer loyalty is most often found in the ability to deliver superior applications.

Now that we know what continuous delivery means, let’s get to my predictions for 2017:


The DevOps Engineer Is An Optical Illusion

IT pros and developers can’t be excellent at everything. Instead, embracing specialization and empowering collaboration in your organization can achieve meaningful and lasting DevOps progress.

Building a collaborative and lightning-quick DevOps organization is a complex but critical business mission today. The technology industry is filled with a host of best practices that promise to help companies achieve this objective. Some of these suggestions make a great deal of sense. But many of the recommendations lead to mediocre results, and organizations simply can’t afford to be half-good when it comes to DevOps.

I’ve been at this a good while, and, as a technology team leader, I’ve found that embracing specialization and empowering collaboration in almost any organization can achieve meaningful and lasting DevOps progress.


Keeping Systems “Poised for Change” with Evolutionary Architecture

At the Agile on the Beach 2016 conference, held in Cornwall, UK, Rebecca Parsons argued that the requirements for improved time-to-market and increased business agility can be achieved by architecting software for real evolvability, keeping systems poised for change, lowering the cost (and risk) of experimentation, maximising visibility and feedback, and aligning the organisation towards the core value proposition.

The second day’s keynote at Agile on the Beach, “Poised for Change”, was presented by Rebecca Parsons, CTO of Thoughtworks. Parsons began the talk by stating that demands in decreasing time-to-market are becoming greater, and although ‘agile’ has been practiced for over twenty years, not all elements of the software delivery process have yet embraced this concept fully. The ability to change quickly and experiment often can be a competitive advantage: