Corporate Architecture Audit.

We assume joint development with the client at the initial stage to determine which elements will be excluded from the audit scope. For example, we may exclude the analysis of cost reduction through service and supplier consolidation or the examination of applications for coding correctness ("code styling", "code review", standards, and best practices) and ease of onboarding new developers.

IT Factory, while considering the framework for which the client organization should build its enterprise architecture, compares four leading methodologies. Based on the set of criteria below and a four-level rating scale, we choose the methodology that will be most effective for the client.

Legend:
1 - provides poor results for the studied area;
2 - provides insufficient results for the studied area;
3 - provides adequate results for the studied area;
4 - provides good results for the studied area.

PHASE 1: Current State Inventory

• Delivering a list of systems and applications to be audited, along with information on their business and
  technological owners and functional descriptions.
• Categorizing these systems and applications into domains such as Sales & Distribution, P&C, Customer Awareness,
  Claims, and Operational Support.
• Developing strategies and guidelines necessary for assessing applications and systems from both technological
  and business perspectives.
• Preparing business and technological questionnaires.
• Facilitating a series of meetings to produce an "application portfolio" document according to a specified
  template, utilizing the prepared questionnaires for data collection.
• Preparing a document presenting the results of the analysis of systems and applications.
• Defining the scope for Phase 2. The "Deep Dive Scope" product is based on the priority list indicated by the
  project sponsor, where auditors conduct deep dives for each area to issue detailed recommendations and repair
  plans.

PHASE 2: Key Findings & Strategies

• Conducting detailed technological and business analysis for selected systems/applications for which deep dives
  are conducted (documentation down to the C4 model level).
• After covering all designated areas, auditors produce a Target Application Landscape document describing the
  target architecture in midterm (3 to 5 years) and long term (5 to 10 years).
• Target Application Landscape Roadmap:
• Defining a set of projects for selected TAL scenarios.
• Analyzing information related to the portfolio of strategic projects and assessing their impact on the chosen
  TAL scenario.
• Monitoring estimations, scope, and priorities.
• Determining the strategic scope of initiatives.
• Creating an action plan (roadmap).
• Estimating the capacity of the production team (capacity plan).

We propose parallel work by two groups of interdisciplinary architects (the size of a team is
tailored to the client needs) to increase efficiency and provide a multi-dimensional assessment of the existing
solution. Each group will include a Lead Architect with expertise in the insurance industry. Supporting Architects are
tasked with acquiring technological knowledge under the guidance of Lead Architects, especially when the Lead
Architects have limited availability.

Here is an example of a team of two specialists designed for one of our clients:

Providing feedback from the client to the person or team performing a given task in the project regarding possible minor errors that were not detected during testing, reporting potential improvements to be implemented in subsequent cycles or reporting changes to the client's requirements.