Continuous Architecture in Practice

Feedback may be discussed regularly, as an important aspect of much of our work in Agile, DevOps, digital product development, Continuous Architecture and in conversations about optimising learning, but how we actually implement effective feedback loops to

Photo by Maximilian Summakate on Pexels In the first part of this article, we outlined what technical debt is, how we can improve our understanding of it, its sources and how to catalogue it.

Preventing technical debt from overwhelming you Ward Cunningham’s 1992 debt metaphor helped explain that the issue with technical debt was never about its existence but the consequences of allowing it to accumulate unchecked.

“The first responsibility of a leader is to define reality.”

Photo by Colton Sturgeon on Unsplash Quality attributes such as performance, security, resilience, scalability and maintainability frequently determine whether a system remains viable over time, yet in many organisations they are consistently overshadowed…

From grand design to guided decision-making Traditional approaches to software architecture don’t work very well with today’s pace of change.

Since Continuous Architecture was first introduced some ten years ago, it has been encouraging to see so many people starting to recognise that the point is the architecture work, not the architects.

This article is part of a series that provides practical advice and guidance on how to leverage the Continuous Architecture approach.

This article is part of a series that provides practical advice and guidance on how to leverage the Continuous Architecture approach.

This article is part of a series that provides practical advice and guidance on how to leverage the Continuous Architecture approach.