DeliveryOn — Project Delivery & Consulting

ABOUT THE PARTNERS

People who have
done the work.

Anton Boyko and Adam Zajicek have spent their careers running software and fintech projects. The person you first speak to is the person who does the work.

PARTNER

Anton Boyko

Project & programme delivery · Enterprise & SaaS

Anton runs complex software projects from start to finish: planning, estimates, build, release and rollout.

He has managed programmes at IBM, a $10M+ middleware portfolio at Red Hat, technical projects at Mews and wealth-platform work at FNZ. He is good at getting several teams to plan together, keeping everyone informed, and using AI tools where they actually help.

BRING ANTON IN FOR
  • Running technical projects and programmes
  • Planning work that spans several departments
  • Keeping everyone informed and in agreement
  • Using AI tools in everyday project work
SELECTED CREDENTIALS
  • PRINCE2 Practitioner
  • Certified ScrumMaster
  • ITIL v3
  • 18 years running technology projects
View Anton’s LinkedIn

PARTNER

Adam Zajicek

Programme leadership · Fintech & recovery

Adam leads large technology programmes, trains the people who manage them, and makes delivery more predictable.

He has 15+ years in technology. He started as a software engineer and went on to lead fintech delivery at FNZ. He rescues programmes that are off track and plans who works on what. He also controls releases, checks project health, and improves delivery processes and makes the development toolchain more effective across teams and organisations (e.g. Jira and Confluence).

BRING ADAM IN FOR
  • Leading complex fintech programmes
  • Rescuing late projects and checking project health
  • Planning people and workload across teams
  • Coaching and developing project managers
SELECTED CREDENTIALS
  • Teams of 50–80+ people per programme
  • Certified Advanced Scrum Master
  • Certified Scrum Product Owner
  • 15+ years in technology and delivery
View Adam’s LinkedIn

SELECTED OUTCOMES

Results, not presentations.

Four outcomes from delivery work the partners ran in their employed roles — not DeliveryOn client engagements. The short story behind each number is further down this page.

€50bn

of assets migrated as part of a major banking implementation in the Nordics.

60–70 hours a day

of manual reporting replaced by automation now used daily by around 70 managers.

A new European market

the first banking implementation, delivered end to end, became the reference for growth in the region.

One delivery model

standardised Jira, Confluence and SDLC practice made collaboration and moving people between projects easier.

WORKING TOGETHER

Complementary strengths.
A shared standard.

We can each run a different part of your project, work on it together, or run a workshop as a pair. Who does what is agreed at the start.

Anton

Projects and programmes, technical delivery, keeping people aligned, and AI in project work.

Adam

Large programmes, rescuing late projects, team planning, decision-making and delivery management.

Together

Practical work that stays close to your teams, your decisions and the result you need.

BEHIND THE NUMBERS

The short story
behind each number.

Each number came from a real programme with real constraints. Here is what was delivered — and what it took.

  1. 1

    €50bn of assets migrated in the Nordics

    A banking implementation in the Nordics included migrating €50 billion of client assets onto the platform. The work ran across several concurrent workstreams and engineering teams, with fixed dates and steering-level reporting.

  2. 2

    Manual reporting replaced by automation

    Delivery status was assembled by hand — 60 to 70 hours of manual reporting across the organisation every day. Automated Jira and Confluence dashboards replaced it; around 70 managers now use them daily, and the hours went back into delivery work.

  3. 3

    A first implementation that became a reference

    Entering a new European market meant the first banking implementation had no template to copy — it had to work first time. It was delivered end to end and became the reference for the follow-on programmes in the region.

  4. 4

    One delivery model across programmes

    Each programme had its own workflows, dashboards and definitions of done, so collaboration and moving people between projects cost more than it should. Jira Cloud adoption and standardised Jira, Confluence and SDLC practice gave teams one shared way of working.

A CLEAR EXPECTATION

The companies named on this page are where the partners have held roles, and the results above were achieved in those employed roles — they are not DeliveryOn client engagements. Naming these companies does not mean they are clients or that they endorse DeliveryOn.