Change Management

Home /
Categories /
Change Management

Why changing the way we architect our solutions?

Since a decade or so, lots of new software engineering practices were introduced mainly to deliver our products faster to our end users. One finds here lean management, agile, devops transformation, Continuous Integration and Continuous Delivery … Why such a trend? because the value is only produced when your product is deployed and used. Everything that is not deployed is just inventory in your souce code base. But one key area was still missing in this massive transformation of our engineering practices and if you end up browsing our Continuous Architecture web site, I guess you already know which area we’re talking about. As the old adage is saying, Rome was not built in a day. We can then perfectly understand that we can not transform all disciplines at the same time. But to complete the journey, we need to finish this off with Architecture. Our creed is “yesterday’s architecture methodologies and processes will not deliver future solutions”. If you take a step back, we can say we build software in a continuous manner today. So let’s adapt our architecture operating model to it !

Start your journey

Start your journey The deployment of the new ways of working (practices, rituals, framework) described in the Continuous Architecture Framework and Toolbox is a major change journey. There is no single pathway to move your enterprise (or part of it) from its current state to the ideal state (or north star) we recommend and which is embodied in the key tenets of the Continuous Architecture Manifesto - edition 1.