Never Skip a Leg Day in DevOps - Part 2
How do you reach the state of "get better at getting better"?
August 31, 2016

Mark Heistek
Devopsense

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. How do you reach the state of "get better at getting better"?

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

A DevOps/Agile Organization

Let's say an Agile company is like a super fit body and mind. You are able to deal with all kinds of circumstances, able to make mistakes, solve them, learn from them and move on. You are able to improve yourself towards the expectations of the outside world, which helps you to stay ahead of competition

An Agile organization is totally DevOps. Everyone is working for the same cause, the product delivered to the customer, based on customer needs and feedback. You are able to respond quickly enough to feedback or changing circumstances. You are able to deliver high quality products and fast.

How Do You Get There?

First you need to have a clear vision and mission statement. For this I'd like to refer to the golden circle of Simon Sinek.


■ WHY does my company exist? What drives the company?

■ HOW do I do this? How do we distinguish ourselves? What makes us unique?

■ WHAT do I need to do to get to this vision? What products do we deliver in what way?

Most companies start with WHAT. They begin to copy "way of working" of other companies and, for example, they implement Scrum in order to become Agile or do micro services, because Netflix did that. They hire bad consultants who are not capable to understand or get to the real drivers (why) of the company. Mostly these consultants want to stay in the company as a long as possible. The mindset of co-creation, transferring knowledge, leave a learning organization behind and do the heavy lifting is not always there. Just like my "Power or Cardio" trainer.

Most companies do not start from inside. What is the core to make it a success? Your company is not equal to other companies. You are unique. You have a different goal or purpose in life than other companies.

Copy Paste

To stay unique, it is important to see how the journey of other companies towards an Agile organization. Take away what you like and implement it your way. A copy is never as good as the original,

By copying, you only copy the practices and not the mindset. Using Scrum does not make you an Agile organization. Also copying buzzwords (tools) and try to implement these will not make you a DevOps organization. Like saying "We will become the Netflix of our country", while you are not offering streaming services. Companies try to steal the golden egg, but not the goose that laid it.

A pitfall of copying DevOps practices is that these practices will be managed by processes and procedures. Companies try to paperize DevOps/Agile by using frameworks and all kinds of procedures.

Procedures and processes are important ... no! They are sacrosanct. Processes help you to uniform your product delivery and therefore adding value to delivery BUT! They are always supportive to delivery. It's mostly not the process what needs to be changed, but the mindset of the company and people. Towards a DevOps mindset.

Read Part 3, outlining the pillars or "muscles groups" of a DevOps transition.

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