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 organizations 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 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 an expert in at least one other needed skill set. 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 performing the needed instrumentation for things like micro-services, containers, and dates 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 cloud services that would enable what they think of as a DevOps pipeline. Most associated with 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 makes 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.

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 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 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. Note: Goods may not always be provided for every Service Offe

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

Search