From product delivery to practical AI adoption.

Kiberry is the Cyprus-based practice of ScrumTrek. Our work on AI projects since 2023 led to Oper8: a method for choosing a process, testing a useful change and deciding what should go into production. Sergei and Askhat, who developed the method, lead the work with clients.

Read the method →Ask for a 30-minute call →

How the work led to Oper8.

Oper8 grew out of ScrumTrek's work with product teams and, more recently, AI projects.

ScrumTrek began in 2008, helping companies improve how they build products and organise delivery. That work taught us to look beyond tools and methods at the decisions, incentives and handoffs that shape a team's results.

In 2023 the team began applying AI to client work. We kept seeing the same practical questions: which process is worth changing, how to test a pilot against real work, and who will own it after launch.

In 2026 we brought that work together as Oper8. The English methodology articles are available on this site. We use the method in workshops, diagnostics and implementation work; the full English book is still in preparation.

Sergei Lipchanskii, Askhat Urazbaev.

Meet the people who developed Oper8 and lead the work with clients.

Sergei Lipchanskii

Sergei Lipchanskii

Founder, Kiberry

Sergei has worked in IT for over 20 years, from software development and engineering leadership to helping companies change how they deliver products. He has worked with Agile teams since 2010.

Today he works on AI-assisted internal tools and helps teams turn promising prototypes into useful processes. He focuses on how the work is organised, measured and improved.

Works with clients on process selection, practical training and the decisions needed to move an AI pilot forward.

Message Sergei on Telegram →
Askhat Urazbaev

Askhat Urazbaev

Co-founder, Kiberry

Askhat graduated from MIPT with honours. For more than 15 years he has worked on Agile practice, digital transformation and product thinking with technology companies, banks and Microsoft. He is the author of Lean Data Science.

Since 2023 he has focused on how organisations can apply generative AI to real work. He works with leadership teams on the choices that shape a programme before implementation starts.

Works with clients on AI strategy, leadership decisions and the design of new ways of working.

Message Askhat on Telegram →

Who does the work on a project.

The project team depends on the scope. Alongside a founder, it may include an agent architect, a DevOps engineer or a trainer.

  1. 01 · Role

    Lead

    One of the founders leads the work with the client and keeps the project tied to the sponsor's decisions.

  2. 02 · Role

    Agent architect

    Designs the technical approach, including how an agent would use data and connect to existing systems.

  3. 03 · Role

    DevOps engineer

    Plans deployment and operations around the hosting and access requirements agreed for the project.

  4. 04 · Role

    Trainer

    Runs workshops and practical learning sessions for the people who will use or own the new process.

We identify the people responsible for delivery in the proposal, so you know who will do the work before a project starts.

Four principles we run projects by.

They explain what we need from a client and what you can expect from us.

Implementation starts only when there is a named process owner on your side.

We need someone in the organisation who can make decisions about the process and bring the right people into the work. If ownership is unclear, we start by establishing it before proposing an implementation project.

We agree where data can be used before the work starts.

The workshop can use anonymised or example cases. A pilot needs a separate discussion of access, hosting, logging and applicable privacy requirements. We record those decisions in the project scope.

Read the English methodology articles before speaking to us.

The articles explain how we select processes, test pilots and think about autonomy. You can use them to judge whether our approach fits your organisation. The full English book is in preparation.

We define the work and its outputs before a project starts.

A proposal states the process in scope, the people involved, the expected deliverables, the timetable and the price. Any assumptions that could change the plan are discussed before we begin.

How to reach us.

Company details

Kiberry is operated by Skill Tech Consulting Limited, registration no. 76164705.

7-F, MW Tower, 111 Bonham Strand, Sheung Wan, Hong Kong SAR China.

Contracts are signed with Skill Tech Consulting Limited. The company has no subsidiary in the EU; its founders work from Cyprus. Our representative in the EU under Article 27 of the GDPR is Askhat Urazbaev (askhat@kiberry.ai).

Read the method →Ask for a 30-minute call →

What we discuss on the call

We can arrange a conversation with Sergei or Askhat to understand what your team needs to learn, build or change and what you have already tried. We will suggest training, an audit or implementation support only if it fits your needs.

Related reading

The Oper8 method

The Data Flywheel, five elements of the flywheel, five principles — the method, in the open.

Read the method

The Oper8 workshop

A two-day workshop to examine a process, estimate pilot costs and benefits, and test an agent on a sample case.

About the workshop

AI readiness and process audit

An online readiness self-assessment, or a process audit to select and plan a pilot.

Explore diagnostics

Let’s
work together

Tell us what your team needs to learn, build or change. We’ll help you choose a training programme or plan implementation.

Discuss your needsTelegram

See the work

Read how a US bid firm chooses which bids to chase from its own track record, and how an executive search firm works with AI agents.

Read the cases
Kiberry

© 2026 Kiberry — the Cyprus-based practice of ScrumTrek

Operated by Skill Tech Consulting Limited, Hong Kong SAR · Registration no. 76164705

PricingPrivacy policy