This learning track explores the change in mindset requires to adopt a collaborative approach that brings everyone involved in delivery together, not just Development and Operations. Geared towards technical and non-technical professionals, this track covers areas such as the business case for DevOps, Continuous Integration, Continuous Delivery, accompanying cultural changes, operational considerations and configuration management. You will get exposure to a hands-on approach to planning, building, monitoring, and maturing a DevOps pipeline. Due to the technology-agnostic nature of this track, you will be able to apply the principles regardless of the chosen technology stack.
Target Audience
Primary Audience: Individuals with a curiosity about the case for and potential of DevOps, and professionals involved in hands-on DevOps implementation.
Relevant Roles: Developers, Testers, Operations leads and team members, Managers, Agile Coaches, Technical Leads, Technical Coaches, Security leads and team members or anyone aspiring to these roles.
Continuous Integration and Delivery
Related Resources
Show Summaries
An overview of four different deployment strategies you can pick from (or match with) depending on your expected outcome.
You might be intending to integrate a new system in your company. However, should you first run the old system in tandem with the new system or you should roll in the new system bit by bit to the people? or maybe you should have a few people interact with the new version before deploying it to the community? These are some of the questions that might be in a manager's head during a new system's integration. Read some system deployment strategies and how they work that managers could choose in this guide.
Introducing DevOps for Agile development practitioners (from a development perspective) - its meaning, origin, and history.
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
A high-level overview of DevOps - its practices, lifecycle, benefits, and challenges to adopt it into your culture.
A descriptive overview of DevOps explaining what it is, when it debuted and why, its lifecycle, how it works, and its key benefits. The article also pinpoints some of the challenges of adopting DevOps and how it is successfully implemented in an organization. Read the article for in-depth details about these and more.
What it is, its value, and how DevOps practices and tools help you move your apps through the entire software delivery pipeline from ideation through production.
Watch this interesting clip about DevOps by Andrea Crawford from IBM. She well-explains what DevOps is, its benefits, and its use cases in an organization stating that DevOps brings the IT development and Operations group together and one of its key benefits is to increase the velocity of how the organization releases products and improve the quality of the product. View the clip for more information on the DevOps benefits and use cases.
The basics to streamline and govern the entire development process, from the brains of programmers onto production servers.
Technical writer and programmer Anthony Heddings delivers a well-detailed beginner's guide article on DevOps principles explaining the general meaning of DevOps, its phases, and how the phases are executed to achieve continuous delivery and high software quality. The cloud engineer notes that DevOps is a set of principles designed to streamline and govern the entire development process, from the brains of your programmers to your servers, and integrates developers with SysAdmins through software development phases such as monitoring, planning, building, testing, and releasing. Find out more about the basics of DevOps in the article.
Detailed specifications of what is expected, the skills required, useful resources and 10 useful tips for new DevOps engineers.
From his real-life experience, Fernando Villalba takes us through an in-depth guide to becoming a DevOps engineer describing what it takes to tap into the industry, the job specifications, the skills required, and useful resources, and also suggests 10 important tips for new DevOps engineers. He notes that DevOps has closed the gap between operations and development allowing developers and operation engineers to collaboratively work together for better business outcomes, real-time delivery of quality software, and getting business ideas to customers faster. If your goal is to make entry into the DevOps space as a DevOps engineer, then this blog is a must-read.
A lot of organizations say they're doing DevOps, but without these six indicators, you're only paying lip service to DevOps best practices.
Becoming a DevOps-focused organization does not require a silver bullet, a lot of organizations claim to be DevOps-centric simply because they use specific tools and follow certain practices, but there are specific DevOps principles and processes that ensure your organization is as optimized and automated as possible. let's find out in the article as technical writer and software engineer Martin Soto lists and explains the principles and operations that indicate an organization is doing DevOps the right way.
An in-depth analysis of these new concepts to help shed light on how and why they originated and what benefits they offer.
According to survey data collected by Gartner in 2016, there is an increasing number of concepts, methods, trends, and approaches designed to help all aspects of the IT industry achieve higher efficiency and productivity but they all come with different benefits. Vladyslav analyzes these Ops describing their key benefits, and how and why they originated. Read the article to understand more about the wide range of Ops and their distinct value when boosting efficiency and productivity in an organization.
How to write and combine individual tasks to automate your software development workflows with GitHub.
Exploring how to get going with this cross-functional way of working that breaks down walls, improves speed of delivery, and increases experimentation.
Release Management
Release Management focuses on planning, scheduling, and controlling the movement of releases through different environments. This cluster covers the strategies and tools needed to ensure that software is released smoothly, on time, and with minimal risk.
Related Resources
Explaining a simple, yet profound, technique that has proven to have a huge impact on improving (DevOps) flow.
The DevOps lesson teaches about the impact of reducing your batch size in DevOps. It explains that most DevOps problems are fundamentally workflow problems and we do not necessarily need innovative technological tools to solve them, there are simple, yet profound, techniques that have proven to have a huge impact on streamlining the batch flow in DevOps. We learn that working in small batches improves the workflow by lowering product-related risks during development and reducing the cycle time, among other merits. Check out the article for more information about DevOps small batches and their benefits.
Using DORA metrics for the wrong reasons will result in poor outcomes. Here's why - and what you can do about it.
Achieve the performance potential that DevOps has to offer by following these nine pillars of practices.
Marc Hornbeek talks about Nine Pillars of DevOps practices, giving examples for each one. In the "Leadership Practices" pillar for DevOps, one of the practices well explained is that leaders intellectually stimulate the team by encouraging them to ask new questions and question basic assumptions about the work. On the other hand, the "Collaborative Culture" practices pillar, an explained practice is that the DevOps system changes follow a phased process to ensure the changes do not disturb the current DevOps operation. Examples of implementation phases include the proof of concept (POC) phase in a test environment, limited production, and deployment to all live environments.
DevOps offers plenty of efficiencies, but it’s no guarantee of business success. Here are three common challenges that require more than just a solid DevOps strategy.
Take your first step towards a fearless organization. And it doesn't have to mean "resign from the one you are in right now".
Using Feature Flags to safely test in production without fear of breaking something or negatively affecting the customer experience.
What qualities and skills define a future-ready DevOps engineer? Hint: It's about people, not code deployment
DevOps leaders will face big changes in tools and architecture. More importantly, they’ll need to help team members develop a more collaborative and transparent mindset.
Don’t risk losing agility by following processes too slavishly and making everything you do too rigid and inflexible.
The benefits of making development teams responsible for building, shipping and operating their applications.
Before you even touch the keyboard it’s a good idea to think about a few points of strategy to ensure success.
To get the best from DevOps, tackle your open source strategy in two dimensions: horizontal and then vertical. Consider this advice on tools and approaches that work .
Cloud Computing
Cloud Computing involves delivering computing resources over the internet, including servers, storage, databases, networking, and software. This cluster focuses on cloud architecture, service models, and deployment strategies.
Configuration Management
Configuration Management is about controlling and maintaining the consistency of software and system configurations. This cluster covers the tools and processes used to track and manage changes, ensuring that systems remain stable and reliable.
Related Resources
A branching strategy can help make an organization's DevOps process more efficient by tracking and managing project tasks. Discover how to create one.
Just as a tree spreads into an array of individual branches, each leading to a unique leaf, a software project splits and proliferates into myriad different versions as it develops. A branch is a point of divergence as well as a copy of the codebase at a given point in time. Developers or IT teams can work with branches to accomplish necessary tasks, such as bug fixes or new features, without affecting other branches or the main codebase. Organizations can establish branches for any purpose, but there are generally five major use cases for branching well-detailed in the article.
Ensuring that an organization knows how its technology assets are configured and how those items relate to one another.
Basecamp conducted a cost-benefit analysis after running on the cloud for over a decade and decided it is time to return to managing their own servers.
System Observability
Monitoring involves continuously tracking the performance and availability of systems and services. This cluster covers the tools, strategies, and best practices for maintaining visibility and ensuring optimal performance in IT environments.
Infrastructure as Code
Infrastructure as Code (IaC) involves managing and provisioning computing infrastructure using machine-readable configuration files, enabling automation and consistency. This cluster covers IaC tools, practices, and benefits.
Platform Engineering
DevOps Practices focus on bridging the gap between development and operations to streamline the software delivery process. This cluster covers continuous integration, continuous delivery, automation, and collaboration techniques.
Operational Resilience
Logging involves collecting and storing log data to monitor and troubleshoot systems. This cluster covers the tools and techniques for effective logging, ensuring that you have the data needed to diagnose issues and optimize system performance.
Site Reliability Engineering (SRE)
Network Design
Network Design involves planning and creating a network infrastructure that supports communication, data transfer, and system operations. This cluster covers principles of network architecture, security, scalability, and performance.