Blog Posts Business Management

Can we leverage architecture in a VUCA business environment?

Blog: Capgemini CTO Blog

Because of VUCA, the way software is delivered has changed dramatically in the last decades. The barriers between software development and operations have been leveled with the introduction of DevOps teams. Simultaneously, continuous delivery methods have cut software development cycles from months, to days, or even hours.

From a distance, everything looks as though it should work fine. However, VUCA software delivery entails a significant risk that I call “Non-Functional Negligence (NFN).” The primary responsibility of a DevOps team is to deliver small pieces of functionality at speed, which often results in neglecting or even ignoring important non-functional topics like re-usability, performance efficiency, and security.

The visible effect of NFN takes time because of the granular evolution of small pieces of functionality. However, at some moment a threshold at which solutions become unreliable due to numerous versions of the same functionality, performance inefficiency, security and legal issues, etc. will be reached. To minimize this risk, three rules should be applied.

First, the delivery platform should be standardized at the enterprise level. This means that for each capability within the platform (especially repository, test, configuration, and change management) an agreed and limited set of tools must be used. If a DevOps team needs to change the platform due to new technologies, this should be assessed at cross-DevOps level before it is incorporated in the platform.

Secondly, an easy-to-use checklist must be applied for each piece of functionality to assess its non-functional fit. This checklist can be used in a formalized way, but informal use is preferred so that potential non-functional issues can be discussed and incorporated into the delivery at the start of the delivery cycle.

Finally, to organize things correctly and sustainably, an architecture role must be in place. The role’s primary responsibility is to standardize the delivery platform in a flexible way and control non-functional topics within individual DevOps team from a cross-DevOps team (i.e., enterprise) perspective. Therefore, I would define this role as “Agile Enterprise Architect.”

By introducing these rules, the distance between enterprise architecture direction and actual solution implementation will shrink, resulting in the delivery of flexible and agile, as well as robust and compliant solutions. Only in this way can complexity be controlled to keep IT aligned with VUCA business expectations.

Leave a Comment

Get the BPI Web Feed

Using the HTML code below, you can display this Business Process Incubator page content with the current filter and sorting inside your web site for FREE.

Copy/Paste this code in your website html code:

<iframe src="" frameborder="0" scrolling="auto" width="100%" height="700">

Customizing your BPI Web Feed

You can click on the Get the BPI Web Feed link on any of our page to create the best possible feed for your site. Here are a few tips to customize your BPI Web Feed.

Customizing the Content Filter
On any page, you can add filter criteria using the MORE FILTERS interface:

Customizing the Content Filter

Customizing the Content Sorting
Clicking on the sorting options will also change the way your BPI Web Feed will be ordered on your site:

Get the BPI Web Feed

Some integration examples