Category Agile and Architecture

AT#10: Technical Debt – the ignored Killer of “Agile” Enterprises

AT#10: Technical Debt – the ignored Killer of “Agile” Enterprises

Trapped in the vortex of digital transformation, almost all industries are facing challenges caused by highly accelerated technology innovation cycles, new and disrupting competitors, and, last but not least, a tremendous amount of technical debt in their vast historically grown IT landscape.

Dave Sag’s blog provides a good summary of what technical debt means.

To deal with this area of tension companies trust in ‘Agile’ gurus that tell them how they must change their organization and culture to become ‘agile’. If we look at the complexity of the application landscape of a typical company it becomes obvious that they simply can’t be agile without renovation projects that make their legacy IT agile.

What you should do:

  • Reduce your technical debt step by step by the renovation of your legacy IT. Agile IT landscapes make companies agile, not agile coaches that focus on culture and organizational aspects.
  • Hire business architects instead of agile coaches.

Previous Posts:

Launch of the Architectural Thinking Framework®

AT#8: Agile goes awry when loosing Balance between Speed and Sustainability

AT#8: Agile goes awry when loosing Balance between Speed and Sustainability

When Agile software development was born in 2001, it defined a set of four principles:

  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

I have worked in several Agile teams where ‘responding to change over following a plan,’ often got misinterpreted to mean “don’t have a plan.”  Those teams often find they waste time by adapting too much.

Read More


close

Please spread the Ideas of Architectural Thinking!