Skip to main content

DevOps Continuous Delivery Architecture (CDA) – Should I get Certified?


A Continuous Delivery Architect (CDA) is a tool-agnostic individual engaged in the design, implementation and management of DevOps deployment pipelines and tool chains that support Continuous Integration, Continuous Delivery, Continuous Testing and, potentially, Continuous Deployment. A continuous delivery architect is also involved in defining or integrating underpinning processes, metrics, APIs and cultural considerations. Getting CDA certified prepares any IT professional engaged in the Continuous Delivery value stream. Not only will they know what to expect but could save a lot of time, money and effort to expedite the systems required to deliver.

While earning a CDA Certification is a great compliment to the DevOps Foundation Certification, you might also find that it can help boost your career or prepare you for very needed positions coming up. The information and perspectives that one gains from shared experiences and class discussions is invaluable. Sometimes it is just as valuable to hear from others with experience about how not to proceed. Come prepared to engage.

Learning Objectives: The learning objectives for DevOps Continuous Delivery Architecture (CDA) key takeaways
  • The principles of Continuous Integration (CI) and Continuous Deployment (CD)
  • Continuous Delivery vs. DevOps Continuous Integration practices
  • Extending CI to CD
  • Principles for architecting a deployment pipeline
  • Engaging Ops in Continuous Delivery
  • Testing and continuous delivery
  • Security and continuous delivery
  • Continuous deployment and automated release
  • Cultural and people consideration and Change resistance
  • Metrics Critical Success Factors, Risks and Challenges, and Getting started
Audience: 
  • CDA is intended for development, quality assurance, security and operational professionals who are engaged in end-to-end DevOps software development from idea conception through live production operations.
  • Anyone involved in or interested in learning about the principles of Continuous Integration and Continuous Delivery
  • Enterprise architects
  • Software developers
  • Build engineers
  • Release managers and engineers
  • Operational and infrastructure teams
  • Security professionals
  • Testers and QA managers
  • IT Managers
  • Project Managers
  • Maintenance and support staff
The Project Management Institute (PMI) Professional Development Units: ITSM Academy is recognized by PMI as a Global R.E.P. Project Management Professionals earn 16 contact hours or PDUs upon completion of this course. A nice value add! 

For more information on this certification click here.

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 …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…