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

March 27, 2017

A recent survey, conducted by Forrester and commissioned by Compuware, showed 96 percent of new business initiatives involve the mainframe. However, the platform is not without challenges. The survey also revealed frustration and concern among development leaders, particularly when it comes to their team's ability to accommodate the speed and agility required to compete in today's digital market ...

March 23, 2017

Mature development organizations ensure automated security is woven into their DevOps practice, early, everywhere, and at scale, according to Sonatype's 2017 DevSecOps Community Survey ...

March 21, 2017

When it comes to food, we all know what's considered "good" and what's "bad". We can all understand this simple rule when eating. But for many, when it comes to software development, simple rules and advice from nutritional labels aren't always there for us ...

March 20, 2017

Monitoring and understanding what software is really doing, and maintaining good levels of software quality is increasingly important to software vendors today. Even a minor bug is capable of shutting down whole systems, and there is a real risk that development cycle pressure competes with quality assurance best practices ...

March 16, 2017

More than half (54 percent) of IT professionals surveyed indicate they have no access to self-service infrastructure, according to a new DevOps survey of 2,000 IT industry executives by Quali.This means that more than half of respondents take a ticket-based approach to infrastructure delivery, impacting productivity and increasing time to market ...

March 15, 2017

Driven by the adoption of cloud and modernization of application architectures, DevOps practices are fast gaining ground in companies that are interested in moving fast – with software eating everything - between "write code and throw it across the wall" to creating more pragmatic mechanisms that induce and maintain operational rigor. The intent behind DevOps (and DevSecOps) is quite noble and excellent in theory. Where it breaks down is in practice ...

March 13, 2017

There might be many people across organizations who claim that they’re using a DevOps approach, but often times, the “best practices” they’re using don’t align with DevOps methodologies. They can say what they do is “DevOps”, but what we’ve found is that many are actually not following basic agile methodology principles, and that’s not DevOps ...

March 09, 2017

The velocity and complexity of software delivery continues to increase as businesses adapt to new economic conditions. Optimizing and automating your deployment pipelines will dramatically reduce your lead times and enable you to deliver software faster and with better quality. Here are three more most common areas that generate the longest lead times ...

March 08, 2017

Every enterprise IT organization is unique in that it will have different bottlenecks and constraints in its deployment pipelines. With that being said, there are some common problem areas that typically produce the longest lead times in your software delivery process. Here are the most common areas that generate the longest lead times ...

March 06, 2017

The findings of an independent survey of IT leaders, application developers and database administrators, conducted by IDG Research for Datical, indicate that database administrators are unable to keep up with the pace and frequency of database changes caused by the accelerated pace of application releases, thus creating a bottleneck and delaying digital transformation initiatives. An overwhelming number of databases administrators (91 percent) and application development managers (90 percent) cited database updates as the cause for application release delays ...

Share this