APAC CIOOutlook

Advertise

with us

  • Technologies
      • Artificial Intelligence
      • Big Data
      • Blockchain
      • Cloud
      • Digital Transformation
      • Internet of Things
      • Low Code No Code
      • MarTech
      • Mobile Application
      • Security
      • Software Testing
      • Wireless
  • Industries
      • E-Commerce
      • Education
      • Logistics
      • Retail
      • Supply Chain
      • Travel and Hospitality
  • Platforms
      • Microsoft
      • Salesforce
      • SAP
  • Solutions
      • Business Intelligence
      • Cognitive
      • Contact Center
      • CRM
      • Cyber Security
      • Data Center
      • Gamification
      • Procurement
      • Smart City
      • Workflow
  • Home
  • CXO Insights
  • CIO Views
  • Vendors
  • News
  • Conferences
  • Whitepapers
  • Newsletter
  • Awards
Apac
  • Artificial Intelligence

    Big Data

    Blockchain

    Cloud

    Digital Transformation

    Internet of Things

    Low Code No Code

    MarTech

    Mobile Application

    Security

    Software Testing

    Wireless

  • E-Commerce

    Education

    Logistics

    Retail

    Supply Chain

    Travel and Hospitality

  • Microsoft

    Salesforce

    SAP

  • Business Intelligence

    Cognitive

    Contact Center

    CRM

    Cyber Security

    Data Center

    Gamification

    Procurement

    Smart City

    Workflow

Menu
    • Enterprise Architecture
    • Cyber Security
    • Hotel Management
    • Workflow
    • E-Commerce
    • Business Intelligence
    • MORE
    #

    Apac CIOOutlook Weekly Brief

    ×

    Be first to read the latest tech news, Industry Leader's Insights, and CIO interviews of medium and large enterprises exclusively from Apac CIOOutlook

    Subscribe

    loading

    THANK YOU FOR SUBSCRIBING

    • Home
    Editor's Pick (1 - 4 of 8)
    left
    Enterprise Architecture's Dexterity Challenge

    Deepak Singh, MD-IT Strategy & Chief Enterprise Architect, Cushman & Wakefield

    Transforming the Role of Technology in Research and Education Institutions

    Khalil Yazdi, Consulting CIO and Principal, Yazdi and Associates, LLC

    Things You Should Consider for a Successful Cloud Migration

    Koray Sonmezsoy, Head of Architecture & Engineering, Li & Fung Limited

    Spring into Action! Growing Enterprise Architecture for Business Seasons

    Martha Tartal, EA, United States Patent and Trademark Office

    Enterprise Performance Management Key Success Factors

    Thomas Rondot, Chief Financial Officer, Danone

    Building an Enterprise Architecture to deliver strategic outcomes

    Kosta Hahladakis, Enterprise Architect, The Reserve Bank of New Zealand

    Building a Strategic Enterprise Architecture- Myth or Reality?

    Regine Deleu, GM Digital Architecture, Auckland Transport

    Automating Architectures for Rapid Delivery and Governance at Scale

    Robert Sang, 20 Digital Architect, Vector Limited

    right

    The Importance of Defining

    Alexander Von Zitzewitz, CEO, hello2morrow

    Tweet
    content-image

    Alexander Von Zitzewitz, CEO, hello2morrow

    The nicest thing you can say to a project manager or your boss is something like “I am done with my task/project”. Everybody loves people who are getting things done. If you do that consistently you will get rewarded and used as an example for those other slackers who are having a bit more trouble with getting things done. On the other hand people who write beautiful, elegant and maintainable code hardly ever get any recognition for that. Nobody really seems to care about the ‘internals’ as long as the software somehow does what it is supposed to do. In a cultural environment like this technical quality, code maintainability and sustainability in general are easily thrown under the bus.

    "A lack of technical quality or technical debt will lead to significantly higher maintenance cost and making it much more difficult to add new features or modularize the system." 

    The Problem

    My point is not to neglect the importance of getting things done, but to have a closer look of the meaning of ‘done’. For most organizations this is defined somehow like this: 

    • The testing department confirms that the use cases work as expected 
    • Performance and user interface seem acceptable 

    Please notice what is missing here? There is no requirement to prove conformance to all defined coding and quality standards. While many companies have formally defined those standards there are hardly ever enforced in a serious way. What's the point, after all? The software is running. Why would you invest any more effort into improving invisible things like technical quality or conformance to coding standards? Well, in some cases this would in deed not make any sense. If you know that the software will never ever be touched or changed again any extra effort for "beauty" would be wasted.

    But on the other hand - how realistic is that assumption? Every non trivial system has bugs, so you would at least have to touch the code to fix bugs.

    The probability of bugs increases sharply with sloppy technical quality. Most systems will also grow over time when new features and requirements are added. A lack of technical quality or technical debt will lead to significantly higher maintenance cost and making it much more difficult to add new features or modularize the system.

    More importantly, if developers know that conformance to coding and quality rules is not as critical as getting the job done they have no incentive to follow the rules. Just the opposite, they will get penalized for doing so because doing things right might take a little bit longer. If they watch other people getting rewarded for being ‘done’ even with lackluster internal quality metrics they will quickly learn their lesson and accept the accumulation of technical debt as a tolerable side effect of getting to the goal faster. Ultimately this leads to a culture where ever increasing technical debt is just baked into the process.

    The people on the top are often afraid that imposing stricter rules might make things even more costly and therefore put even more time pressure on the projects because that will presumably lower the immediate cost impact. Of course technical debt comes with a high interest rate, so all short term savings will be eaten by much higher cost of change down the road. In fact we can assume that the uncontrolled growth of technical debt will easily double or even triple the lifetime cost of a software system. 

    How to Solve It 

    So, what can we do about all that? I'd say the solution is quite simple. We need to be more specific about the meaning of ‘done’ by adding a third bullet point to its definition: 

    • The testing department confirms that the use cases work as expected 
    • Performance and user interface seem acceptable 
    • The code conforms to all rules regarding technical quality and architecture 

    The usefulness of such an extra rule should be obvious. In all other engineering disciplines you check the quality of all parts before you integrate them into a system. We would not have safe airplanes, cars or trains without some serious efforts to control quality on all levels of operation. Only in software development it is quite easy to get away with bad internal quality because it is mostly invisible.

    If you add the third bullet point nobody can claim to be "done" without proving conformance to the rules. Now people have a strong incentive to follow quality and architecture rules throughout the development process. And rewarding people who are "done" makes much more sense because cheating by taking on technical debt in favor of speed is not an option anymore. Interestingly enough you will find that following the rules all the time will soon become second nature to all developers and lead to increased velocity over time. Avoiding the accumulation of technical debt will also avoid the interest payments down the road, which will increase team efficiency and agility and keep the cost of change on a reasonable level.

    In a future article about technical debt, I lay out some ideas for a small and simple rule set that can be used out of the box. In addition I also look at the accumulation of technical debt as a strategic tool to achieve important goals outside of the domain of the development process. 

    Weekly Brief

    loading
    Top 10 Enterprise Architecture Technology Consulting/Service Companies - 2020
    ON THE DECK

    Enterprise Architecture 2020

    I agree We use cookies on this website to enhance your user experience. By clicking any link on this page you are giving your consent for us to set cookies. More info

    Read Also

    Advancing the Chemical Industry through Digital Transformation

    Advancing the Chemical Industry through Digital Transformation

    Jan Mandrup Olesen, Global Head of Digital Business, Indorama Ventures
    Cultivating a Sustainable Future through Collaboration

    Cultivating a Sustainable Future through Collaboration

    Jiunn Shih, Chief Marketing, Innovation & Sustainability Officer, Zespri International
    Mastering Digital Marketing Strategies

    Mastering Digital Marketing Strategies

    Tasya Aulia, Director of Marketing and Communications, Meliá Hotels International
    Building a Strong Collaborative Framework for Artificial Intelligence

    Building a Strong Collaborative Framework for Artificial Intelligence

    Boon Siew Han, Regional Head of Humanoid Component Business & R&D (Apac & Greater China), Schaeffler
    From Legacy to Agility Through Digital Transformation

    From Legacy to Agility Through Digital Transformation

    Athikom Kanchanavibhu, EVP, Digital & Technology Transformation, Mitr Phol Group
    Change Management for Clinical Ancillary Teams: Aligning Practice with Policy and Progress

    Change Management for Clinical Ancillary Teams: Aligning Practice with Policy and Progress

    Ts. Dr. James Chong, Chief Executive Officer, Columbia Asia Hospital – Tebrau
    Digital Transformation: A Journey Beyond Technology

    Digital Transformation: A Journey Beyond Technology

    John Ang, Group CTO, EtonHouse International Education Group
    Building A Strong Data Foundation: The Key To Successful Ai Integration In Business

    Building A Strong Data Foundation: The Key To Successful Ai Integration In Business

    Richa Arora, Senior Director Of Data Governance, Cbre
    Loading...
    Copyright © 2025 APAC CIOOutlook. All rights reserved. Registration on or use of this site constitutes acceptance of our Terms of Use and Privacy and Anti Spam Policy 

    Home |  CXO Insights |   Whitepapers |   Subscribe |   Conferences |   Sitemaps |   About us |   Advertise with us |   Editorial Policy |   Feedback Policy |  

    follow on linkedinfollow on twitter follow on rss
    This content is copyright protected

    However, if you would like to share the information in this article, you may use the link below:

    https://enterprise-architecture.apacciooutlook.com/cxoinsights/the-importance-of-defining--nwid-2048.html