Continuous Delivery Architect (CDA)

Continuous Delivery Architect (CDA) – “The Role”

Continuous Delivery Architects are engaged in the design, implementation, and management of DevOps deployment pipelines. This infers the inclusion of all tools and tech to support Continuous Integration, Continuous Delivery, Continuous Testing, and even Continuous Deployment.

Subjective viewpoints and misunderstandings of what is involved and how to orchestrate a pipeline can lead an entire organization in the wrong direction. Every “Continuous Delivery Architect” should consider formal education and certification to ensure that they do not proceed in error.

I see in practice that the emphasis is on the tooling and although that is a key element, even more critical is the process flow, the APIs, and the inclusion of practices to ensure things like security, compliance, and resilience are built into the orchestrated automated pipeline. Let us not forget the importance of CULTURE and the role that plays.

There are three primary ingredients for continuous delivery:

Automated configuration management – to be able to stand up a machine and software with one command

Continuous integration – automate builds, tests of builds, and fast recovery of the trunk when failures are detected

Automated testing – tests help to prove whether a release candidate is NOT ready for production and if problems do occur in production then tests are improved

Architecture affects continuous delivery in many ways including

Testability
Deployability
Reliability

The CDA must have a broad understanding and a holistic perspective and at the same time seek to learn the ecosystems of people, processes, and technologies that produce business and customer outcomes.

Shatter the silos! If you are an architect and you have DevOps Foundation certification, be sure to take the next step with your CDA education to move your organization and the world forward!

Comments

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group. As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. ...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...

Search