The architecture review process is (or at least should be) a critical part of any IT project – especially considering the seemingly ever increasing level of complexity most IT architects face. It is a key opportunity for stakeholders to ask the ‘why this’ or ‘how about that’ questions with the dual goal of increasing their understanding as well as checking whether the architect is on the ball. It is a game of hunting down all of the critical assumptions – get them wrong and your project will be well on its way to failure.
Any architecture is built on a set of assumptions. We don’t know everything, and we need ways to limit our scope, so we use assumptions to reduce the unknowns and control our commitments. But in the process of making assumptions, we may incur ‘technical debt’. Continue reading “Architecture Reviews, Technical Debt, and the Cloud”
