Skip to main content

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 are the API’s and the inclusion of practices to ensure things like security, compliance, and resilience are built into the orchestrated an 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 – test 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 eco systems of people, process and technologies that produce business and customer outcomes. 

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


Comments

Popular posts from this blog

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

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

ITIL 4 – Mapping the Customer Journey

All service providers are in the business of customer and user experience. It is not enough to compete on products and services, how services are delivered is as important as what is delivered.

The customer journey is the complete end-to-end experience customers have with one or more service providers and/or their products through the touchpoints and service interactions with those providers. In order to focus on the outcomes and on the customer/user experience, service providers are seeking to master the art of mapping their customer journey. Doing so allows them to maximize stakeholder value through co-creation of value throughout the entire value chain.

The customer journey begins by understanding the overall macro-level of steps or groups of activities that generate the need for interaction between the customer and the service provider. These activities begin at “Explore” and end with “Realize” where the value is actually being consumed by the end-users.
The Band of Visibility