Never Skip a Leg Day in DevOps - Part 1
How DevOps/Agile is sub-optimized
August 29, 2016

Mark Heistek
Devopsense

When I was an active football player, I took my job as a goalkeeper seriously. During summer I started preparing myself for the new season. I went running and I practiced my skills so I could be in good shape as soon as the new season started.

One summer I wanted to do extra training. As a goalkeeper you not only need to have stamina and speed, but also a strong body to deal with all clashes and falling. Therefore I decided to work on my physical strength. I subscribed for a gym. I thought it would be wise to start with my upper body, training my arms, neck, shoulders, back and stomach muscles. I skipped the leg training, because I did some running as well.

During the season I kept going to the gym to strengthen my upper body. One day I made simple save and during landing something twisted in my knee. The injury came from nowhere, took me two months to recover and I lost my position. I needed to start all over again. The injury was a complete mystery to me and I told myself it was bad luck.

During my recovery I went to the gym again but this time I hired a trainer. This trainer asked me, "Power or cardio?". My answer was power to strengthen my upper body. He printed out some exercises and he was off. Based on this advice I started to do my exercises.

A few months later I was able to restart playing, only this time in the second team as I got used to the game. In the second match I twisted my knee again. This time very badly and I was out for 9 months.

I needed to start all over again. I thought this was bad luck, again. But this time I wanted to come back stronger than ever. I hired a trainer who will guide my whole recovery process to become the best goalkeeper in my competition. The trainer asked for my ambitions and goals. I explained I want to be back as the number one goalkeeper and become champion with my squad. He created a tailor made training program and to my surprise there were exercises to train my legs as well. He said "never skip a leg day". I told him there was no need to train my legs, because I wanted to do running exercises as well. He disagreed on this and said, "train your legs too and it will make you be a better athlete, increase your range of motion, reduce your risk of injury, improve your balance and you'll run faster and longer".

What Does This Have to Do with DevOps?

As a company you want to win the competition by creating awesome products for your customers. The competition is hard nowadays. Big companies are caught up by start-ups and products are more subject to change as they used to be 20 years ago. Products come and go and need continuously adjusted to meet customer needs. To meet customer needs we need to make sure that we organize in a way that we can take advantage of modern technology. Even better, we can fulfill customer needs before they actually know they have the need.

For many companies, technology and the way they are organized are not in sync to meet customer needs. Therefore there is long feedback loop and this leads to low quality, which is costly.

For example, startups have the ability to meet customer needs more than enterprises for several reasons:

■ In a start up, the creators are close to the creation, which means the products fit the needs of the customers really well.

■ The purposeful nature of start ups, people who work there are more motivated.

■ They can easily adopt new ways of working and technology. This is also a must, otherwise they won't survive.

■ The feedback loop is very fast. There are no otiose departments in between.

■ They embrace change to amplify the feedback loop.

If products need to change rapidly you need to be able to do the change. You need to be flexible in making changes. To survive or to be number one in the market, you need to be become an Agile organization.

For me Agile means DevOps. A way of system thinking to amplify the feedback loop and come to come to a culture of continuous experimentation and learning as described by Gene Kim in his DevOps blog.

DevOps means a mindset of:

■ Working together to create great products.

■ Working together as a team where everybody has his own competencies and talents.

■ Working together in your whole organization, both business and IT.

■ Working together with your customers to understand their needs.

DevOps means a mindset of getting better at getting better. You need to get better to fulfill customer needs, and therefore you need to get interested in what your customer wants and make sure the feedback loop will be as short as possible.

Read Part 2, answering the question: How do you reach the state of "get better at getting better"?

Mark Heistek is Head of Delivery and Founder of Devopsense.

The Latest

June 23, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 3 covers how Agile enables you to grow and adapt to change ...

June 21, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 2 is all about speed ...

June 19, 2017

Earlier this year, DEVOPSdigest featured a list of expert opinions on the essential steps to become agile. Now that we have an idea on how to achieve agility, however, we have to consider why. What's the payoff? With this question in mind, DEVOPSdigest asked the experts — including analysts, consultants and vendors — for their opinions on what are the most important advantages of being Agile ...

June 15, 2017

In the development community, creating additional efficiency through improved collaboration has been prevalent for some time. But despite the head start on the rest of the corporate world when it comes to collaboration, many organizations function today as they did 15-20 years ago. Since time is money in the tech world, outdated collaboration is a huge missed opportunity ...

June 14, 2017

Given the efforts we put in these days to deconstructing monolithic applications, and using distributed microservices to make us more agile, the potential for app performance to take a nosedive because of unseen (and unanticipated) network congestion and outages is only getting greater. There is help at hand, though, in the form of new ways to program network awareness directly into your code ...

June 12, 2017

What if you discover a fatal error or an exploit in your app? What if your app is down during a crucial time? As a developer, how you react to a crisis can mean the difference between minor blip and an embarrassing or costly company blunder. Here's a crisis management plan to get things right when they go wrong ...

June 08, 2017

Recently, the results from SmartBear Software's annual survey, the State of Code Review 2017: Trends & Insights into Dev Collaboration were released. One point I found interesting is that it suggests only 66 percent of organizations can get releases out on time. Why are the other 34 percent struggling to get releases out the door? ...

June 06, 2017

Today's app development landscape is competitive and expensive. Thousands of apps are released each month, and user acquisition and retention are costing app developers millions. User abandonment is one of the main battles of every app developer — as every lost user means another wasted investment ...

June 05, 2017

Developers love using containers to build, run and ship applications in a flexible and simple way. However, the technology has received backlash for not being as secure as other (traditional) methods, such as Virtual Machines (VMs). Securing containers and securing VMs requires a completely different process. Below are four key differences between securing containers versus securing VMs ...

May 31, 2017

DevOps results in improvements in software delivery performance, according to a new first-of-its-kind study by CA Technologies to quantify the benefits for companies that combine DevOps methodologies with Cloud-based tools and delivery mechanisms ...

Share this