• 10 MDs + 6MD talent tech assessment

Audit scope

• **Business architecture audit (1 MD)**
  • Understanding the product growth history from the technology perspective
  • Understanding of the value chain and how the product generates revenue
  • Business domains and hi-level processes
  • Organization structure
  • Non-functional characteristics (opening hours, number of users, expected throughput, data security requirements, sensitivity to solution outages, speed of implementation of changes)
  • Document output: Gain a solid understanding of the business architecture and document the scope above.
• Software architecture categories (3 MD)
  • C4 model: from Context to Containers to Micro/Services (first 3 layers, no code)
    • Service Dependencies
    • Front-End / Backend business logic split
  • Patterns / Anti-Patterns usage
    • Scalability (possibility to scale up based on client/user load)
      • Resource Utilization, Bottleneck analysis and optimization, Scaling planning and management
    • Stability and Availability (downtime ratio)
    • Maintainability (monitoring)
      • Monitoring and alerting systems, Logging and tracing, Performance and resilience metrics
    • Security best practices
      • Access management and authentication, Data encryption at rest and in transit, Container and Kubernetes cluster security
  • Document output:
    • Gain a solid understanding of the software architecture, document the top data flows in the C4 model ent the dependencies.
    • Analyze the current software architecture and the alignment and risks with best practices in Kubernetes microservices.
  • Do we have right software architecture and technologies to move forward? Quality of the architecture: final rating.
• Infrastructure architecture categories (3 MD)
  • Kubernetes review
    • Cluster Design overview
    • Resource management and scaling
    • Versions upgrade plan
  • Release management & coordination: Time to deploy and deployment quality process
    • Deployment & configuration process
    • Build and deployment pipelines
    • Deployment process automation
  • Testing:
    • Testing process and quality: Change failure rate
    • Load testing and stress testing
    • Coverage in unit/integration and end to end tests
  • Incident management process quality
    • Observability, Hotfixing: Time to recover
  • Do we have right tooling and infrastructure to move forward? Quality of the infrastructure: final rating.
• Summary (3 MD)
  • Technical roadmap
    • Highlight the most solid parts
    • Assess the potential technological risks regarding the technical roadmap
    • Propose the changes in the current technical roadmap of the product:
      • name of the improvement change
      • severity/impact
      • Mitigation proposal
      • Effort in time and resources
    • Based on the solid understanding, compare the existing technical stabilization roadmap of the product with your findings and proposed changes
    • Ultimately, evaluate the necessary resources and time required to achieve better stability, quality, speed, and scalability of the product → create a proposed roadmap.
  • People aspect
    • Include a brief subjective rating on the scale 0..10 regarding people technical skills after talking to them.

Please note, each category will be rated on the scale 0 .. 10 and explained by supporting data or information gathered. In parallel, each category will naturally contain a solid suggestion as a proposed fix.

Note from the company: Team recently has recently internally reviewed all problematic areas and developed stabilization plan targeting to finish winter 2025 and saying that after soft will be functioning normally and we can grow. Key is to correlate findings with stabilization plan, assess its direction and see what is missing.

Requirements

Full cooperation between the Cloudfield and company representatives, transparent information and data.

Required documents and sources

Product Background & Business Architecture

• Chief Technology Officer (CTO)

Sources:

• Product roadmap (historical and current)
• Technology stack documentation (current and future)
• Major migration or rewrite project plans (mentioned existing plans from meeting)
• Business domain models
• Process flow diagrams