Never Skip a Leg Day in DevOps - Part 3
Getting in Shape for DevOps
September 02, 2016

Mark Heistek
Devopsense

Start with Never Skip a Leg Day in DevOps - Part 1

Start with Never Skip a Leg Day in DevOps - Part 2

The Muscle Groups of a DevOps Transition

When you start to work out in order to get your body and mind in shape, you need to know why you want to do it, how you want to do it and what you need to do. In my case it was:

WHY: Become the best goalkeeper in the competition in order to become champion with my squad.

HOW: Get to a certain level of physical strength and mental well being.

WHAT: Follow a balanced routine to train all muscle groups based on best practices and with help of professionals.

By answering the why, how, what questions I had a clear understanding of how to achieve my goals. The injuries were caused by an incomplete view of what to do to reach my goals. I was optimizing the upper body and neglected my legs. I did not reach out to good trainers to help me to understand my "why" translating this to my "how" and "what".

The neglection of "legs" or "skipping the leg day" happens a lot in companies where they transform towards a DevOps organization. I am going to explain this based on the pillars or "muscles groups" of a DevOps transition.

To transform towards a DevOps organization you need to cover all DevOps "muscle groups". Let's dive into these groups.

Company Organization
Profit driven towards Culture-Purpose driven

Purpose driven companies gives them the ability to measure customer satisfaction. Well defined measures give manageability and therefore a feedback loop to learn and improve your product or product delivery. If you are not purpose driven you can cannot measure progress of your product.

For more insights I'd like to refer to this Financial Times' article of Simon Caulkin.

Work Methodology
Waterfall structure towards Agile/Scrum

The waterfall methodology of building software products can be compared by constructing buildings.

■ You analyse what to do and arrange budget for developing the building

■ You hire a few architects to design the whole building

■ You hire a construction company to build the building based on the design and specifications

■ Finally you open the doors and hand over the keys to the new residents

This process can take months or years.

Since software products need to change rapidly to meet customer needs and external circumstances, the waterfall methodology takes too much time.

You need to move away from creating big blocks of software and start to deliver small products which can be improved based on customer feedback. An Scrum framework can be used to achieve this. Working is short periods to shorten the feedback loop.

Implementation of the Product
Manual delivery towards Continuous Delivery

Delivering increments to add value to your product means doing the same process over and over again. This can result in dull and repetitive manual work. There is also a huge possibility of making mistakes.

Tools to build, test and deploy your software can do the dull and repetitive work for you. They'll do it faster, make no mistakes and therefore a higher quality.

By automating the delivery process you can reuse the process as much as you like and get instant feedback, so you can immediately respond to improve the product.

Architecture
Monolith towards Micro Services

Creating changes to a monolith application can have a huge negative impact to your product. A monolith application is build with many dependencies, so it is hard to change just a small part without taking into account the effect on other parts in the application. It can break quickly.

Breaking down your application towards micro services makes it much easier to make small changes. When it breaks it will not affect other micro services, so your application will just not work in a small part. Benefit of this you can do changed independently and when it breaks, you can fix it quickly.

Environment
Autocratic towards Autonomy

Delegate to the team. Do not tell how to do stuff, but coach them to improve themselves, so they can improve the product. Let the team decide how to change the product. Give trust to the team and give them time to proof this trust.

If you want to get better in doing things better, you need to fail and learn. Failing is not an option, it is a must.

You Can't Change Overnight - It Takes Time and It Will Hurt

The change towards an Agile organization with a DevOps mindset is a natural one. It can not be captured in processes and procedures.

DevOps is more than just a way to build better and faster software/products. It's more than just a cultural shift in the way we work. DevOps is a self-organizing force that becomes part of your company DNA, driving complete organizational change. Therefore you can never skip a leg day in DevOps. All muscle groups matter and it will make your company a better athlete, increase its range of motion, reduce its risk of injury, improve its balance and it will run faster and longer.

Practice every day. Take small steps. Fall, get up, learn and get 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