Scaling Product Delivery From Small Teams to a Multi-Product Organisation

The challenge

The New Business and B2C delivery teams each began with approximately three people: a Product Owner, a developer, and a QA specialist. New Business was responsible for one emerging product, while B2C supported six customer-facing product areas. As demand and opportunity increased, the teams needed a delivery model that could scale without returning to siloed knowledge, duplicated work, unclear ownership, or uncoordinated releases.

My role

As Senior Project Manager and delivery lead, I introduced the estimation and Scrum framework, coordinated teams and vendors, supported Product Owners with budgets and procurement, led requirements discovery, and planned delivery sequencing, schedules, and releases.

Delivery approach

1. 1Introduced a shared estimation methodology so Product Owners, developers, and QA could make realistic commitments against available capacity.
2. 2Used Scrum to timebox development, establish delivery cadence, and connect project deadlines with clear team promises.
3. 3Created common review, knowledge-sharing, and retrospective practices so changes, dependencies, successes, and failures became visible across teams.
4. 4Aligned release planning and clarified responsibility for communicating requirements, dependencies, and product decisions.
5. 5Prepared the budgetary and technical case, requirements, delivery plan, vendor coordination, and proof-of-concept foundation for moving from native Android and iOS development toward Flutter.
6. 6Kept the cross-platform work within its evidence boundary: implementation was progressing when I left, but the later scope changed and I do not claim delivery of the completed migration.

Business value

• Grew each delivery team from approximately three to approximately 15 people
• Expanded the New Business portfolio from one product to six products on the market
• Expanded B2C responsibility from six to nine customer-facing product areas
• Consistently delivered team commitments by the agreed deadlines during my tenure
• Built organisational confidence that supported continued investment, broader responsibility, and team growth
• Established shared knowledge, aligned releases, regular retrospectives, clearer ownership, and less duplicated work