“Rugged” describes software development organizations that have a culture of rapidly evolving their ability to create available, survivable, defensible, secure, and resilient software.

Discover how teams and organizations manage work effectively using the Kanban methodology. Learn how to get started with Kanban.

The adoption of IT technologies has increased exponentially over the last few decades. Nowadays, the need to create quality web applications while

That multiweek cycle that suits the dev team isn’t always a great fit for devops

There is an enormous amount of confusion and misinformation about Kanban. This article will clear up some of the major misconceptions that surround this topic. Let's go through them one by one. You have to choose between Kanban and Scrum The most common misconception I’ve found is that people think you have to choose between

The Bot Framework in Microsoft Teams links applications and services to instant messaging and group chat. Microsoft launched Teams, a collaborative platform in Office 365, in March 2017 and has recently added new functionality enabling use for ChatOps. It has also announced that Teams will replace Skype for Business.

Learn how ChatOps functions as an integral part of IM teams' processes, bringing the incident workflow into one place helps to keep teams aligned.

ChatOps is the idea of communicating across organizations at a velocity that allows for the smooth operation of DevOps functionality

devsecops.org is an informational site for security and business practitioners looking for innovative ways to incorporate security at scale.

blue-green deployments have been practiced at places like Amazon for 10+ years. They’re a safe, proven, method. Now, blue-green deployments are not a silver bullet, but there’s an element of usefulness to them.

A deep dive case study into the Google SRE Site Reliability Engagement Model with and overview and specific examples.

Discover Site Reliability Engineering: read an interview with Ben Treynor Sloss

DevOps Research and Assessment (DORA) is a long running research program that seeks to understand the capabilities that drive software delivery and operations performance. DORA helps teams apply those capabilities, leading to better organizational performance.

Continuous Integration is probably the most widely known in this list of practices. It is about compiling/building/packaging your software on a continuous basis.

Continuous Delivery means you build software in such a way that it can be released to production at any time

The deployment pipeline is the key pattern that enables continuous delivery. A deployment pipeline implementation provides visibility into the production readiness of your applications by giving feedback on every change to your system. It also enables team members to self-service deployments into their environments. Learn how to create and manage a deployment pipeline, and how to use the crucial information it provides on the bottlenecks in your software delivery process so you can work to continuously improve it.

While working on the Devops Cookbook with my fellow authors Gene Kim,John Willis,Mike Orzen we are gathering a lot of “devops” practices. For some time we struggled with structuring them in the book. I figured we were missing a mental model to relate the practices/stories to. This blogpost is a first stab at providing a structure to codify devops practices. The wording, descriptions are pretty much work in progress, but I found them important enough to share to get your feedback.

I am always surprised by the urban legends around DevOps. One of my favorites is, If you implement a DevOps methodology, you can stop doing test. People

What is the goal of Continuous Integration? Is it to enable Continuous Delivery of the code developers’ produce out to users? Yes, eventually. But first and foremost it is to enable ongoing test an…