Scope that did not match
I joined after discovery. What had been sold and what the client actually needed did not line up, and the product was at an early build stage.
Uzhhorod · Remote · EET
Bohdan N. Senior Project Manager
bohdan.neymet@gmail.com · t.me/bodco · linkedin.com/in/bneymet · github.com/bodco · Uzhhorod, Ukraine · Remote · EET (UTC+2/+3)
Summary
From unclear scope to stable production. 7+ years in IT delivery, most recently on a fintech payments product for an enterprise client in Latin America: I set the real scope, took it to live production with 50,000+ users and led a cross-functional team of 13 through a full handover. I also build and open-source the tooling I run projects with.
FLIGHT STRIP · FINTECH LIVE
- Status
- In production · card infrastructure
- Users
- 50,000+
- Team
- 13 · cross-functional
- Method
- Hybrid Agile + fixed scope
- Handover
- Done · auth stream ongoing
- Discovery
- Scope
- Build
- Live
- Handover
7+ yrs in IT delivery since 2019
50,000+ users on a product I took to production fintech · payments
13 people in the cross-functional team I led through full handover
up to 20 people in distributed teams I coordinated fixed-price and T&M
Projects: Reset the scope, shipped it, handed it over
Fintech payments product for an enterprise client in Latin America. Client and product stay confidential.
Before meDiscoveryInitial discovery and sale, scope still unclearScopeResetWhat was sold against what the client neededBuildHybridAgile and fixed-scope phases, one planLiveProductionCard infrastructure, real usersHandoverIn-houseTeam moved to the client, production stable
One plan, one voice
Set the real scope, turned requirements into prioritized work, covered analyst and product owner duties, and stayed the single point of contact. When scope spiked, the client saw the trade-offs before anything moved.
Live, then handed over
The product runs on card infrastructure with 50,000+ users. When development moved in-house, I led a structured handover of the team and production stayed stable.
PM Control Tower v1.6.1 · beta · MIT
Projects: I built the system I run delivery with
PM Control Tower · Open source (MIT) · v1.6.1 beta
An open-source Claude plugin and Notion template for project managers. It collects context, preps meetings, drafts reports and tracks risks on daily, weekly and monthly schedules, and gives live tips during calls. Every project fact sits in one config file, and a human approves every outgoing message.
Built and used daily on a live client project.
tower.bodco.pm · github.com/bodco/pm-control-tower
22Claude skills, project-agnostic
11linked Notion databases
1config file per project
dailywork report, reply draftsscheduledweeklyoverview across projectsscheduledmonthlyclient report draftscheduledon calllive tips co-pilotlivealwaysa human approves every messagegate
Work Experience: In delivery since 2019
-
Senior Project Manager, Volya Technologies (formerly Knubisoft)
One enterprise account end to end: scope reset, production launch, team handover, ongoing production support.
Delivery
- Took over a fintech payments product for an enterprise client in Latin America after discovery, reverse-engineered what had been sold against what the client actually needed, set the real scope and drove it from early build to live production on card infrastructure, now serving 50,000+ users.
- Owned the full delivery lifecycle (requirements, planning, release management, budget, risk, quality) across hybrid Agile and fixed-scope phases.
- Led the structured handover of the development team to the client as the engagement moved in-house, keeping the production system stable.
Client and team
- Single client-facing point of contact for enterprise stakeholders across time zones, handling conflict resolution and decisions under tight deadlines.
- Led a cross-functional team of 13: turned client requirements into prioritized work and, when scope spiked, reset priorities and walked the client through the trade-offs.
- Covered analyst and product owner duties where the project had no dedicated role.
Platform and releases
- Ran the payment authorization component as a separate ongoing workstream, including production support.
- Owned all App Store Connect and Google Play publishing for the product. Earlier, delivered a portfolio of mobile apps through to release on both stores.
- Designed and open-sourced PM Control Tower, built through daily use on this project.
-
Project Manager, IT Outsourcing Company (name under NDA)
Fixed-price and long-term T&M delivery for US-based clients, with account management for an enterprise engineering organization.
Delivery
- Delivered fixed-price and long-term T&M projects for US-based clients, with budget tracking on fixed-price contracts.
- Gathered and clarified requirements, did business analysis, and produced work plans, schedules and estimates.
- Reported progress and risks to stakeholders across the full delivery cycle.
Client and account
- Account manager and primary point of contact for a US-based enterprise client's engineering organization: resourcing, staffing and partnership topics.
- Ran regular partnership reviews with client leadership and tech leads: agreed priorities for the next delivery phase, tracked action items, coordinated scope paperwork between both sides.
Team
- Coordinated cross-functional, distributed teams of up to 20 people.
- Managed staffing and backfills: interviewed QA automation candidates and kept a bench of previously used engineers for fast ramp-up.
- Coordinated contractor access and tooling with the client, escalating recurring access issues until they were resolved.
Skills: What I bring to delivery
-
Delivery and methodology
- End-to-end delivery
- Agile
- Scrum
- Kanban
- Waterfall
- Hybrid
- Full SDLC
- Release management
- Change management
- Risk management
- Quality management
-
Commercial
- Fixed-price
- T&M
- Budget tracking
- Requirements
- Estimation
- Scope management
-
Stakeholders and teams
- Stakeholder management
- Enterprise clients
- Conflict resolution
- Prioritization
- Distributed remote teams
- Staffing and backfills
- Mentoring and onboarding
-
Domain
- Fintech
- Payments
- Card infrastructure
- Production support
- Mobile releases (App Store, Google Play)
-
AI-assisted delivery
- Claude skills and scheduled routines
- Notion and Jira integrations
- Reporting and meeting prep automation
- Human-in-the-loop communication
-
Tools
- Jira
- Confluence
- Linear
- Trello
- Notion
- Slack
- Figma
- Claude (Cowork, MCP)
- App Store Connect
- Google Play Console
How I work: Four habits behind the delivery
01
No surprises for the client
Risks and scope changes reach the client from me, early and with the options on the table.
02
Trade-offs before work starts
When scope grows, the client sees what moves and what it costs, then decides.
03
One source of truth
Every project fact lives in one place, not in my head.
04
Built to be handed over
Priorities, decisions and access are documented as we go, so the team and the system can run without me.
Education
- Master's degree, Cyber SecurityUzhhorod National University
- Master's degree, PhysicsUzhhorod National University
Certifications
- Google Project Management (Coursera)
2021 · Agile Project Management, Project Initiation, Project Planning, Project Execution - IAMPM: PM Hard Skills Planning, PM Hard Skills Release
2023
Languages
- EnglishAdvanced
- UkrainianNative
- HungarianBeginner
Contact: Write to me
Telegram is the quickest way to reach me. Email and LinkedIn work too.
Uzhhorod · EET (UTC+2/+3)