Skip to main content

Continuous Delivery Architecture, A Rainbow of Tools

Image
By
The Age of Architecture 
Architecture is one of those universal roles that no matter the job, it's critical you have a good understanding of the architecture to be successful in both development and operations. As with any architectural role, there are so many moving parts that if you can’t see the machine for the cog you’ll never be able to master your craft. The problem seems that because of the siloed nature of the business, no one but those in architecture gets the lay of the land, it is in this challenge that continuous Delivery Architecture was created to help ALL practitioners understand not only the big picture but the why and how every component is vital to success.

What’s In The Toolbox
To help you get an idea of the sheer quantity of tools that will be at your disposal I’ll give you the highlights reel. It starts with what we call a collective body of knowledge. This is a collection of materials (books, blogs, websites, etc.) to help you on your journey to learn. Then comes a bevy of concepts from DevOps to Continuous Delivery to help drive some common language. We’ll kick things off on the strategic track to ensure we have a unified vision and goals. See what we did there? We’ll cover topics such as pipelines, the seven pillars, culture, strategy, approaches, and roles. Then we blend strategic and tactical considerations to ensure we have the right process wrapped around everything and some principles and methods we can apply to measure the effectiveness of your execution. You’ll see topics such as ChatOps, Retrospectives, Change Management, Pitfalls, Branching and Merging, Design Patterns, Microservices, Containers, CI/CD, Gating, Database, Scaling, Monitoring, Testing Strategies, Automation, Orchestration, Chaos Engineering, Release Strategies, and so much more. We walk you through every consideration from planning to production delivery and everything in between. Finally, we ask important questions along the way and leverage practical applications to reinforce learning with exercises and capstone projects. In the next few minutes, I’ll attempt to elucidate some of these areas.

Learning About The Usual Suspects
DevOps teaches us that we should strive to always create a culture of collaboration and trust in every activity. This often starts with understanding each other’s roles and challenges. A critical step in this is to start with a foundational understanding of all the practices at work in your organization. You know what approaches I’m talking about, Waterfall, Agile, ITIL, DevOps, Lean, and many others. When we understand the powers at work in our organization, we understand how we complement each other’s capabilities. Yes, even Waterfall can have a place in the organization. You’ll learn more about these roles and how they can interact and why they generally don’t work. The key here is to bring value to any approach.

Continuous Delivery Culture
Seven distinct pillars will outline the components of your journey to create a continuous delivery culture. Each will not only add value to the overall structure but provide multiplicative returns with their application in concert with each other. They are a lot like Power Rangers, pretty awesome by themselves but when you combine them, WOW! This course will cover each pillar in detail as well as guide you through the questions you’ll need to ask so you can integrate them into your current processes. The big takeaways here are how you can complement and enhance current operations, this will help you build towards a more successful transformation.

Back It Up With Best Practices
One of my favorite things about all ITSM Academy courses is that they focus on making sure we have the best practices outlined and we show you how to execute what you’ve learned. It made such a difference for me in my career, it’s the reason I became an instructor for them. The best part is that those best practices are a combination of not only industry standards but tried and true methods from actual practitioners so you know what you are learning will already resonate and be impactful in your organization. They even cover the wrong ways to do things so you will notice negative patterns and how to stop them before they take hold. Then we fold adoption challenges and quick wins into the equation so that you know what you're getting into and how to effectively execute with a clear path to success. One last benefit I’ll mention which is invaluable is that in every class there is a mix of other practitioners. This means you’ll get the added benefit of thought diversity of others who may have the same questions or have overcome some of the challenges you have or will face so you’ll get genuine experiences, not just theory. That alone has been worth its weight in gold.

Double CDA Rainbow, What Does It Mean?
The breadth and depth of the content with Continuous Delivery Architecture is substantial. If you could only take one course after your DevOps foundation course, let it be this course. It will give you an end-to-end overview of the entire process and dive into each and every component that makes up continuous delivery. This course will give you the greatest bang for your buck. Architects, developers, engineers, and leaders alike will find this course a comprehensive and significant bolstering to their current skill set and will bring them up to speed on seeing the entire picture and how each part contributes to its operation. After all, isn’t that one of your greatest challenges already?



Labels:

Comments

Post a Comment

Popular posts from this blog

Four Service Characteristics

By
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...
Post a Comment
Read more

What Is A Service Offering?

By
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.      ...
Post a Comment
Read more

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

By
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...
Post a Comment
Read more