Skip to main content

Continuous Delivery Architect – T-Shaped, PI-Shaped & COMB skills Required!


Is your organization transforming with AGILE, ITSM, DevOps or LEAN and looking forward to optimizing a Continuous Delivery Pipeline? 

Do you want to be a Continuous Delivery Architect?


This is an amazing and exciting time where you can dream and build upon what you have and develop the “COMB” shaped skills that will shape your future!

The “2019 Upskilling Report for Enterprise DevOps Skills” reinforces that organization not only need “T” shaped skilled practitioners or even “PI” shaped skillsets. Many high performing organizations are looking for individuals that have “COMB” shaped skillsets. An individual with “COMB” skills would have a broad base of knowledge forming the top of the comb and then also have multiple expertise areas which gives the shape of a comb. You can start developing your skillsets or those of your team to shape individual career opportunities and also to shape the future of your organization.

Expanding your skills is particularly needed for those involved in any way with DevOps and Continuous Delivery Pipelines. I suggest by beginning with “T” shaped skills. This means you get a broad understanding of the business and the overall end to end Value Stream but also that you develop at least one very in-depth skill. This could be technical or other, but you would be expert in at least one other needed skillset. Then move onto a “PI” shaped skill set where you would have that broad understanding of the end to end system but now have depth into two main areas. For example (Development and Security) might be your in-depth skills. And finally, now you are ready to look into how you could develop further for “COMB” shaped skills.

When a group of DevOps Foundation Certification candidates were asked “What do you think of when you hear the title “Continuous Delivery Architect? What is that role?” Most associated the role of defining the tooling and performing the needed instrumentation for things like micro-services, containers and cloud services that would enable what they think of as a DevOps pipeline. Most associate to the design of this pipeline and in part, this is true.
In truth, a “Continuous Delivery Architect” (CDA) is a tool-agnostic individual who not only is engaged in the design but also must have a key role to play in the implementation and the management of the toolchains and ecosystems that support Continuous Integration, Continuous Delivery, Continuous Testing and ultimately Continuous Deployment.  In order to optimize the throughput, and ensure the speed to value a CDA should have an integral role and be involved in defining or integrating underpinning processes, metrics, APIs and more.  All of this while having a keen sense of cultural considerations make The “Continuous Delivery Architect” role, the key to the success of a DevOps Continuous Delivery Pipeline.

This is an amazing and exciting time where you can dream and build upon what you have and develop the “COMB” shaped skills that will shape your future!

ITSM Academy's CDA course in our virtual, instructor-led classroom is open for enrollment.

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…