Siarhei Trukhin
Delivery Manager · Independent · Kraków
linkedin.com/in/sergeytruhin ↗

Your AI-native SDLC, run like it has a deadline.

I plan, run and report delivery end to end — Scrum and Agile cadence wired to AI-assisted engineering practice, so the roadmap stays true and the releases stay on time.

st-dm status --portfolio
uptime
— since 2015-12-25
last role
Senior DM · 3 projects · fintech & enterprise
team
0 → 110 BA·PM·Dev·QA
discovery
7 accounts, one framework
domains
banking · betting · media
availability
open for B2B · NDA ok
// what I run

Delivery, covered end to end.

  1. stage/01before sprint 1

    Discovery & scoping

    Requirements, estimates, risk — settled before the first sprint starts.

  2. stage/02cadence

    Scrum & Agile delivery

    Backlog, sprint cadence, stakeholder reporting — run without the ceremony overhead.

  3. stage/03every stage

    AI-native SDLC

    AI-assisted estimation, review gates and reporting woven into every stage of the lifecycle.

  4. stage/04loop

    Release & retro

    Shipping, measuring, and feeding results straight back into the next sprint.

// recent work

AI in the delivery process: two measured cases

ai/01

AI code review: ≈ 47 hours saved every month

  • −15%review time, 26.5 → 22.5 min
  • ≈ 47 hsaved per month
  • 46%of AI comments accepted by developers

Context

Product team, ~700 pull requests a month. Review was a steady source of queue time.

What I did

Introduced AI as a first-pass reviewer on every PR, so human reviewers start from a pre-filtered list of issues instead of a blank diff. Architectural decisions stay with humans.

Measured over three months.

ai/02

From Jira ticket to reviewed pull request: ≈ 1 hour for a standard ticket

  • ≈ 1 hper standard ticket, start to pull request
  • ≈ $20model cost per ticket
  • 3human approval gates

Context

Engineering team that needed a repeatable way to take a ticket to a reviewed pull request with AI, without losing control.

What I did

Led the design and rollout of a Claude Code workflow: ticket check, plan, build, independent review, ship.

  • Requirements are written down before any code, and the review checks the diff against them.
  • A different model reviews the code than the one that wrote it.
  • Nothing is pushed without the developer's approval.

Proof

On one complex ticket the run took 2 h 11 min and ≈ $80, added 81 tests, and the independent review caught 3 defects, including a latent bug the tests had been masking.

Standard-ticket figures are typical values. Complex tickets vary too much for an average, so one measured run is shown. About 15–20 tickets taken end to end so far.

A few examples

case/01 · fintech portfolio

Scaling a delivery org from zero

Built and scaled cross-functional teams — BA, PM, Dev, QA — from 0 to 110 people across a portfolio of fintech and enterprise projects, without losing delivery quality along the way.

team.size110
0 · 2021-11 → today
case/02 · discovery

A Discovery framework that travelled across 7 accounts

Designed a Discovery Phase framework for one engagement, then rolled it out across 7 client accounts — standardising how scope, risk and estimates get settled before a single sprint starts.

case/03 · hiring

Hiring the people who run delivery

Built and ran the PM / PO / DM hiring pipeline for a fast-scaling delivery organisation — 50+ candidates assessed to date.

// how I work

Background & approach

Siarhei Trukhin

Independent Delivery Manager, sole proprietorship in Poland. From November 2021 I ran a portfolio of fintech and enterprise projects at Andersen Lab — banking, betting and media clients, end to end across Discovery and Delivery; before that, IT Project Manager in T&M and Fixed Price models. I started in December 2015 with a one-person IT venture, and that hands-on start is still how I work: Scrum and Kanban where they earn their place, AI woven into the SDLC where it actually saves time, never process for its own sake.

Education: Sukhoi State Technical University — Web Programmer.

// credentials

Certifications

cert/04 Anthropic Academy × 5 2026 · tap a course to open it
// git log --career
  1. HEAD now

    Independent Delivery Manager

    Sole proprietorship in Poland — STDM, B2B engagements.

  2. a1f3c9e 2026

    Anthropic Academy × 5

    Claude 101, Claude Code in Action, Claude with the Anthropic API, Model Context Protocol, Agent Skills.

  3. 7c2e0b4 2026

    Professional Scrum Master I

    Scrum.org.

  4. 9d41b7a 2024

    IBM AI Developer

    Professional Certificate, IBM · Coursera: 7 courses, started in 2023.

  5. 3c7e2a9 2021

    ICAgile Certified Professional — Agile Product Ownership

    ICP-APO, ICAgile.

  6. 4e9a1d2 2021

    Senior Delivery Manager

    Andersen Lab: fintech & enterprise portfolio, Discovery to Delivery.

  7. 2b7f6c1 2020

    IT Project Manager

    Cross-functional teams of 20–30 people, T&M and Fixed Price.

  8. 0000001 2015

    init: solo IT venture

    Discovery, build and support for 15+ SMB clients — end to end, alone.

// working together

How engagements usually start

  • Based in Kraków, Poland (CET) — remote-first, overlaps comfortably with most of Europe.
  • Languages: English, Polish, Russian, Belarusian.
  • Independent, B2B engagement — scoped around a portfolio or a single delivery track, not a headcount swap.
  • NDA before the first call is never a problem.
  • Jira
  • Confluence
  • Azure DevOps
  • GitHub
  • Slack
  • Claude Code
  • Claude Agent SDK

Do you work with regulated or compliance-heavy clients?

Yes — banking and fintech portfolios are where most of the last four years have gone.

Can you join a project that's already in flight?

That's usually how it starts — most engagements begin mid-stream, not from a blank page.

What does the first step look like?

A short call, on Telegram or wherever's easiest for you — no proposal before it.