AIM Scrum

The AIM methodology uses Scrum as the main framework for managing AI transformation of organizations.

AI transformation is an evolutionary process where the organization learns to work in new ways. It's impossible to define all steps in advance: value emerges through trial changes and their validation in practice. That's why AIM uses Scrum — an iterative and adaptive way forward, creating measurable value step by step.

We don't change Scrum as a framework. We only clarify its application in the context of AI transformation to make the process transparent, strategically aligned, and tied to business value.

Definition

AIM-Scrum is a lightweight framework that helps people, teams, and organizations create value through adaptive changes to the operational model using AI. It connects the strategic level of decisions (Transformation Roadmap) with the operational level of implementation (backlog and sprints), ensuring continuous movement from strategic intentions to concrete results.

In short, AIM-Scrum requires that the AI Business Partner maintains an environment where the following cycle is executed:

1. AI Transformation Owner clarifies business goals based on decisions recorded in the Transformation Roadmap and translates them into concrete changes to the operational model, adding them to the Transformation Backlog.
2. Transformation Team during the sprint turns selected changes into increments that create measurable value.
3. The Team and stakeholders inspect results, update priorities, and adjust the backlog — and if necessary, the roadmap itself.

This cycle repeats as long as the transformation consistently delivers business value.

Value

Measurable result for the business, achieved through process change using AI or preparing processes for its application.

Value attributes:

• expressed in numerical indicators (hours, money, SLA, error rate, NPS, etc.);
• recorded before and after implementation;
• forms the basis for business goals and sprint goals;
• used to assess progress on the Transformation Roadmap.

Transformation Team

Transformation Team (Scrum Team) — a cross-functional group responsible for creating AI transformation increments. It unites all competencies needed to change operational model processes and obtain measurable value.

Composition:

• AI Transformation Owner — responsible for maximizing value, formulates product goals, and ensures backlog alignment with the Transformation Roadmap.
• AI Business Partner (AIBP) — ensures framework compliance, transparency, and strategic connection between council decisions and team actions.
• Process Developers — specialists with knowledge in business processes, data, and AI. They implement changes that create value.

Cross-functionality:

The transformation team has all competencies to:

• understand current processes and their limitations,
• adapt them using AI,
• implement changes in departments,
• measure and confirm value,
• maintain connection between operational changes and company strategic goals.

Events

Sprint

An iteration of operational model changes. Each sprint is aimed at achieving a measurable goal related to business goals and priorities defined in the Transformation Roadmap. Sprint duration is fixed (usually 2–4 weeks). At its end, an increment is created — a process change that brings value.

Sprint Planning

The transformation team determines which changes from the Transformation Backlog, aligned with the Roadmap, will be implemented in the sprint, and formulates the Sprint Goal. Special attention is paid to goal measurability and connection with business goals. Stakeholders participate in the discussion so the team has everything needed to achieve results.

Daily Scrum

Short synchronization of process developers. Progress, obstacles, and next steps are discussed. The main goal is transparency and daily adaptation within the team, not reporting.

Sprint Review

The team demonstrates implemented changes to stakeholders and links them with corresponding Roadmap directions. Main focus — actual value and feedback that may influence priorities of next sprints.

Sprint Retrospective

An event for improving team work and transformation process. In AIM, special attention is paid to how sprint results contributed to Roadmap progress and what can be improved to make the "strategy → actions" connection stronger.

Artifacts

Product

The company's operational model — how the organization creates and delivers value.

Business Goal

A long-term goal of changing the operational model, expressed in business metrics and agreed with the Transformation Roadmap.

Example: "Reduce order processing time by 50% over a year by implementing AI in the supply chain".

Transformation Backlog

An ordered list of operational model changes, aligned with Roadmap goals and directions. Each backlog item has strategic justification and measurable value.

Items may include:

• process changes using AI,
• formalization and digitization of operations,
• implementation of metrics and observability,
• training and employee engagement,
• experiments to reduce uncertainty.

The backlog is dynamic: updated after each cycle when the team receives new data on value or strategic priorities change. For prioritization, the SERFD.AI framework may be used.

Sprint Backlog

Selected items from the transformation backlog and the team's plan to achieve the sprint goal. It serves as the tactical level of executing the strategic course.

Sprint Goal

A short-term goal of changing a specific process, measurable and verifiable within the sprint.

Example: "Automate classification of incoming requests and reduce manual work by 30%".

Increment

An improvement to the operational model process with or without AI application, creating verifiable and measurable value. Each increment records progress toward business goals and advances the company along the Transformation Roadmap.

Definition of Done

An increment is considered complete if the change is implemented in the operational model, available for use, and confirms value in measurable indicators.