Skip to main content
Phase concerned
Diagnosis
Objective

To ensure that modernization is aligned with the organization's mission, vision and objectives

Description

Following key aspects could/should be addressed during Context Analysis:

  1. Organizational Goals & Strategy (focus area)

    • Mission & vision alignment: how the application to be modernized contributes to the company’s purpose.

    • Strategic priorities: e.g., cost reduction, faster time-to-market, innovation, compliance, sustainability.

    • Business KPIs: revenue growth, customer satisfaction, operational efficiency, risk reduction.

    • Target state: what the organization expects from the modernized application (agility, resilience, scalability, user-centricity).

  2. Business & Value Chain Role

    • Is the application mission-critical (core to business operations) or a support tool?

    • Which business processes depend on it?

    • Expected business outcomes from modernization (e.g., reduced downtime, faster releases, new business capabilities).

  3. Regulatory & Legal Context

    • Compliance with industry standards and legal frameworks (e.g., GDPR, ISO 26262, HIPAA).

    • Risks of non-compliance (fines, reputational damage, operational disruptions).

  4. Organizational & Cultural Context

    • Company culture (innovation-driven, risk-averse, cost-focused).

    • IT governance (decision-making structures, funding models).

    • Stakeholder objectives (CxO, product owners, compliance, operations).

  5. Technology & Ecosystem Dependencies

    • External vendors, SaaS, APIs, and infrastructure.

    • Roadmap alignment with technology strategy (cloud-first, on-prem, hybrid).

    • Interoperability with other enterprise systems.

  6. Market & Competitive Drivers

    • Competitive pressures requiring faster delivery or differentiation.

    • Benchmarking against peers.

    • Emerging market needs and innovation opportunities.

Representative illustration(s)
Image
Logo context analysis
FAQ

Is there a recommended methodology to support this activity ?

The GQM (Goal–Question–Metric) framework helps organizations conduct modernization in a goal-driven, measurable, and transparent way.
It ensures each modernization step is anchored in organizational objectives and provides decision-makers with a dashboard of aligned metrics to support both strategic commitment and continuous monitoring.

A key principle is that metrics must be integrated from the beginning of the modernization journey — starting in the diagnostic phase — to establish a baseline and ensure every modernization step can be evaluated against organizational goals.

How GQM Works in Modernization

Goal – Define modernization objectives

  • Business-oriented and long-term.

  • Examples: Improve maintainability, Reduce downtime, Accelerate time-to-market.

Question – Translate goals into evaluation points

  • Clarify what needs to be asked to know if the goal is being achieved.

  • Example: How frequent and predictable are deployments?

Metric – Provide measurable evidence

  • Indicators that answer the questions and track progress.

  • Examples: Deployment frequency, MTTR, technical debt ratio, defect density.

The Role of the Dashboard

By structuring modernization with GQM, organizations can build a dashboard of metrics directly aligned with strategic goals:

  • Decision support: CxO stakeholders can commit to a modernization roadmap knowing how it contributes to business objectives.

  • Transparency: Every modernization initiative can be traced back to an organizational goal, with measurable evidence of impact.

  • Monitoring contribution: Over successive iterations, the dashboard shows how modernization delivers value — whether in reliability, agility, cost efficiency, or innovation capability.

  • Continuous alignment: If organizational priorities evolve, the dashboard ensures modernization efforts can be realigned quickly.