ManyĀ business leaders are planning to makeĀ DevOps the cornerstoneĀ of their ITĀ transformation strategy. But, as surprising as it might sound, skepticism abounds regarding how major vendors address the DevOpsĀ transformation challengesāthey confuse DevOps with continuous delivery (CD) infrastructure.
“We wanted DevOps and we got after a nine-month-long implementation a continuous delivery platform which speeds up IT operations without significant business value. How differently can you help?” the senior businessĀ executive of a major financial institution in New York sarcastically asked me during a conversation threeĀ monthsĀ ago.
The businessĀ executive is right: DevOps isn’t a technology as I’ve been implementing it, it’s primarily an accelerated application delivery approach implemented in the form ofĀ a technology-enabled application delivery operationalĀ model.Ā Adam Jacob, CTO of Chef, substantiatesĀ that fact in “The Secret of DevOps: It’s Always Been About People, not Technology,” when he says, “DevOps is about bringing together all the people you need to build and run your business effectively, and empowering them to move as quickly as possible towards their goals.”
Agile Admin’s Ernest Mueller in, “DevOps: It’s not Chef and Puppet,” confirms Adam’s point: “Chef and Puppet are individual tools that you can use to implement specific parts of an overall DevOps strategy if you want to use themābut thatās it. They are fine tools, but do not solve DevOps for you.”
How can we implementĀ DevOps in line with business leader expectations? Three Amazon Web Services (AWS) Design Patterns I developed can help to get the best of DevOps on AWS cloud: Software Organization Factory, Digital Organization Factory and CD Infrastructure Factory.Ā This article discusses the Software Organization Factory.
The Foundation of DevOps Value: Consequences to IT Service Delivery
Before delving into these AWS design patterns, a quick reminder of what DevOps is, its value propositions and, more importantly, what changes are needed in how IT services are delivered.
The Ignored DevOps Business LogicĀ We All Must Consider
The combined effect of cloud adoption andĀ the rising digital economyĀ isĀ changing competitive environments; itĀ forcesĀ business leaders to focus onĀ innovation and market responsiveness as theĀ competitive differentiators.
The fact of the matter is,Ā by facilitatingĀ access to technology, cloud acceleratesĀ entrance of several thousands of tech startups that take advantage of the recent technology innovations to substitute traditional products and services into digital.Ā This creates a contextĀ where new entrantsĀ increasingly compete with established brands, forcing business leaders to seek value paradigms other than IT efficiency.
The businessĀ executive argues, “In these new markets, our concern is to increase customer value by delivering the right services to the right segments at the right moment. You guys need to change the IT paradigm; ITĀ alone does not create that kind of value.”
Then, what should be changed in today’s IT approach?
The Two Dimensions of Modern IT: The OperationalĀ Model and the ContinuousĀ DeliveryĀ Infrastructure
TheĀ new IT paradigm advocated in my recent book, “Rethink Your IT with DevOps: The Complete Guide to Aligning Your IT to DevOps,” is the idea that business value results from two dimensions: organizational agility and technology efficiency. In other words, it defines modern IT as a two-dimension asset including the operationalĀ model and the continuous delivery infrastructure.
The timely delivery of innovation transcends IT issues; it not only cuts acrossĀ your sales, marketing, post sales, application development and Ā IT operations, but also demands concrete answers as to how to accelerate business prioritization, decision-making and problem solving.Ā The operational model is where business and IT people, processes, practices and tools are combinedĀ to create agile and cross-functional environments. The following exhibit shows a typical DevOps operational model:

Organizational flexibility for the sake of flexibility doesn’t make sense unless technology is leveraged to speed processes. This is whereĀ CDĀ infrastructuresĀ come into play; throughout the delivery process, they build on IDEs to accelerateĀ coding and testing, on versioning tools to convert software version into releases, on continuous integration (CI) tools to build releases and on delivery pipelines to ensure continuousĀ delivery.
So, what is DevOps?
DevOps is a Technology-Enabled Application Delivery Model
DevOps is a combination of value, principles, processes and practices shared not only by developers and IT operations but alsoĀ by the business. The goal is to help theĀ organization deliver the right service to the right market segments at the right moment.

As I’ve been implementing it, it’s a cross-functionalĀ application delivery model involving the business and IT and enabled by continuous delivery infrastructures.
By enabling and automating agile practices, the continuous delivery infrastructure makes the operationalĀ model agile and provides the businessĀ with the flexibility and velocity needed to meet competitive challenges.
Design PatternsĀ asĀ DevOps Implementation Engineering Framework
As suggestedĀ by the business executive, today’s DevOps implementations struggle to deliver the promisedĀ business benefits. The reason is, the operational model dimension is ignored in favor of tools and infrastructure.
Another reason is, DevOpsĀ is young and is still at the early stage of the technology maturity model; the expertise and engineering methodologies to implement it as what it isāa technology-enabled application delivery modelāare lacking. That’s where DevOps transformation design patterns help.
What are DevOps Transformation Design Patterns?
In this article, the term DevOps transformation design patterns refers to general reusable architectures addressingĀ specific DevOps strategy. They’re not necessarily implementable solutions, their primary goal is twofold:
- Offer a neutral language for designing and implementingĀ technology-enabled operationalĀ models
- Offer an engineering approach that reduces design and implementation duration and effort
They’re formalized architecture design and implementation best practices for DevOps and platform-as-a-service (PaaS) services.
Design Pattern as DevOpsĀ Implementation Engineering Methodology
To meet its goalsātechnology-enabled application delivery modelāthe design pattern is structured around four items includingĀ purpose, Ā principles, general solution and implementation techniques.
Purpose:Ā Clarifies the purpose of the design pattern along with the DevOps strategyĀ to address.
Principles: Are best practices formulated as rules and beliefs supposed to guarantee expected DevOps strategy benefits? They’re the determinants of the solutions to implement the DevOps strategy.
General solution: Are blueprints resulting from the application of principles? They summarize the functional and technical architecture of the DevOps platformĀ to implement.
Implementation techniques: What are recommended technical approaches, solutions and tools to implement the general solutions?
Why AWS? Why wouldĀ it be theĀ catalyst for DevOps value?
Ā AWS-ome Design Patterns That Will Change DevOps Implementation
AWS offers such a rich, varied and easy-to-implement services portfolio that it would be unfortunate not to take advantage of it to modernize IT. The rationale underpinning the value businesses can derive from their DevOpsĀ transformation experience with AWS is summarized in the following figure:

It’s the belief that:
- CertainĀ principles determine the AWS services needed to deliver the application delivery model (ADM)Ā architecture that guarantees value.
- The implementation of the ADMĀ using these AWS services results in AWS-basedĀ DevOpsĀ platforms that tangibly deliver expected benefits.
The Four DevOps Principles that YieldĀ AWS Value
Let’s explore the principles I’ve been using to make CIOs happy with their AWS cloud:
- Think holistic, not only IT:Ā Reminds that transformation isn’t only about IT but the entire organization’s value stream from marketing and sales to development and IT operations.
- Think cross-functional, not only IT:Ā Reminds that the bottom line is to set up a cross-functional application development environments to accelerate business prioritization, problem-solving and decision-making, and meet time-to-value objectives. They’ll be the core value propositions of the DevOps platform.
- Make it agile, flexible, and speedy:Ā Reminds that agility, flexibility and speed are the catalysts for competitiveness and business value. They’ll be part of the DevOps platform.
- Think PaaS:Ā Reminds that AWS provides varied services for implementing state-of-the-art CD infrastructure.
Let’s illustrateĀ three AWSome design patterns that’ll change DevOpsĀ experience with AWS!
ImplementĀ a Startup Mindset with the Software Organization Factory
The purpose is to implementĀ DevOps strategies focused on time-to-market and time-to-value.Ā It’s adapted for tech startups.
To implement theĀ startup mindset, the DevOps four principles for AWS are implemented as follows:
- Think holistic and cross-functional, not only IT:Ā Relevant business and IT resources are put together in a single and dedicated service development team supported by appropriate Scrum and XP agile practices.
- Make it agile, flexible and speedy: PaaS services building on agile practices and AWS infrastructure-as-code are provided to make application delivery processes agile, flexible and speedy.
- Think PaaS: Ā AWS infrastructure as code and DevOps tools are combined to implement a CD infrastructure in the form of a PaaS platform.
The DevOps platform resulting from the principles application is illustrated below:

The “Startup Mindset” platform is structured around three components including the cloud-enabled operational model, PaaS and the CD infrastructure.
The operational model builds on a three-stage application delivery life cycle:
- Ā Plan & measure: It mobilizes business users, development, QA and operations staff on business prioritization issues using agile practices such as Scrum product backlog planning or XP’s user stories.
- Develop & Test:Ā It mobilizes business users, development, QA and operations staff across the development life cycle using agile techniques such as Scrum iterations, XP’sĀ test-driven development (TDD) and behavior-driven development (BDD).
- Release & Deploy: ItĀ leverages continuous integration practices to build and test releases prior to deploying to production.
- Monitor & Improve: It’s outsourced to keep the service development team on its core business: developing software.
The CD infrastructure combines the followings services:
- AWS CodePipeline and CodeDeploy to set up the delivery pipeline.
- AWS infrastructure as code including CloudFormation, OpsWorks and Elastic Beanstalk to generate the CD infrastructure.
Summing It Up
The DevOps business benefits are real, yet, it’s young and isĀ still at the early stage of the technology maturity model. The expertise and engineering methodologies needed to implement it as what it isāa technology-enabled applicationĀ delivery environmentāare lacking.
DevOps design patterns such as the software organization factory fill the gaps of today’s transformation practices:
- They provide the architect team and the executive team a neutral language to discuss the business, technological and technical challenges and solutions.
- By pointing out the agile practices to leverage, they simplify and accelerate the design and deployment of the operational model.
- By pointing out the AWS services and features to leverage they facilitate the design and implementation of the CD infrastructure.
The DevOps implementation process described in this article is fully documented in my recent book, “Reinventing Your IT with DevOps: The Complete Guide to Aligning Your IT to DevOps.”
In my next article I’ll tackle the Digital Organization and the CD infrastructure design patterns.




