04. We analyse existing architecture
Why we analyse existing architecture
To avoid formulating a new, expensive solution when the existing one serves this purpose.
Our activities at this stage
- Identifying problems of the existing solution.
- Defining which new components we need (a new back office is a component).
- Considering the complexity of the integration.
- “What happens if this part of the architecture does not work?” Assessing architecture stability.
- Recalculating the financial impact.
- An updated architecture
- A list of modules, systems, SaaS, functions, integrations, and data. The list also includes a description of how they can be applied, and their owners.
- An account of essential low-level technologies
- A licence overview
- New/affected contracts
- A list of new competencies required
- Start with what you already have.
- Do not try to create wonderful shiny new architecture that is easy to follow and precise. The goal of the architecture is to minimize costs, cut the implementation period, and ensure the cheapest operation.
- Seek solutions to individual problems in existing systems, integrations and data. Check whether these solutions can be changed at a reasonable price and in an acceptable timescale. Build new components when you cannot find a simple solution.
- One new thing replaces two old things. If this is not the case at your company, you should draw up a compelling calculation of the financial impact of doing so (e.g., payback in 12 months).
- If you are implementing a solution in phases, you should clearly define what happens if only the first stage is completed.
- KPMG Integrovaný design
- Scaled Agile Framework (SAFe)