Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Digitalisation - Complex for All the Wrong Reasons

DZone's Guide to

Digitalisation - Complex for All the Wrong Reasons

· DevOps Zone
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

Here's a short article that I wrote in 2011 for Dansk IT about digitalisation. The TL;DR version is "understand your enterprise architecture".

- - -

In my role as a software developer, Iʼm often asked to automate existing business processes and transform them into computer systems. Sometimes this is about replacing systems that are solely manual in nature and sometimes itʼs about replacing manual systems that have a digital core like an Excel spreadsheet. Digitalising these processes can be as simple as creating a way to capture the essential data, implementing some automated processing and ensuring that the resulting data is stored centrally for others to use. Unfortunately though, life is never that simple and digitalisation becomes a complex task for all the wrong reasons.

The goal of most digitalisation efforts is usually related to reducing cost, improving efficiency or simply making somebodyʼs life easier. Achieving this normally requires centralising some aspects of the data and the associated process, ultimately requiring people to work together who are often in different teams and often in different locations. To complicate matters, you need to deal with the data silos that each of those separate teams have built up over the years. Essentially, itʼs *their* data that they have complete control of and itʼs *their* version of the truth. Iʼve seen this everywhere from large investment banks where each business area has their own definition of what should really be common reference data, through to organisations where each department has a different view of their customers. Creating a single consolidated source of truth typically requires teams to relinquish some of their control and likely some of their data too. Reaching agreement on the definition of common concepts is one thing, but getting teams to give up some of their perceived power is another entirely.

Agile might be the hottest thing in software development at the moment, but having an understanding of the enterprise architecture is crucial for any digitalisation effort, particularly if it spans an organisation and crosses internal boundaries. My advice? Focus on the end-goal and donʼt get caught up on the politics, particularly if youʼre an outsider looking in.

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

Topics:

Published at DZone with permission of Simon Brown, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}