Three-month sprint to MVP

In the client's organization there was an internal support tool — a technical support tool that served as a link between the team handling advertising campaigns and internal business partners. This system worked well with simpler configurations, but as the number of campaigns and their complexity grew, it fell short of expectations in terms of flexibility and scalability.

‍

So far, campaigns have been created in the Demand-Side Platform (DSP) model, where the entire process — from configuration to launch — was carried out with the participation of operational staff. The new initiative was to change that layout: build a web application that would allow end users to plan, configure and manage campaigns on their own. The goal was to reduce campaign implementation time, reduce reliance on technical teams, and increase service availability for smaller advertisers.

‍

The project was carried out by a team spread between Warsaw and California. Its members included a front-end developer working with Team Connect, who played a key role in delivering the MVP.

Although the project did not have a fixed deadline, the team set itself an ambitious goal: to build a working MVP in three months. Thanks to efficient cooperation with stakeholders and an iterative approach, we managed to achieve it in the stipulated time — without quality cuts and while maintaining high efficiency of the team's work.

‍

Our specialist was responsible for the front-end layer of the application, but his role was not limited to writing code. As the most experienced member of the team, he served as a technical leader: he supported less experienced colleagues, cared about code quality, proposed architectural improvements, and participated in defining good design practices.

‍

The project presented typical challenges for the MVP phase: the need to quickly deliver features that will also be the basis for further development; careful scope management; prioritization while maintaining high quality. The team dealt with them efficiently thanks to good alignment and clearly defined priorities — the project went smoothly and without disruption.

From the beginning, the project was built with scalability in mind — both technical and team.

‍

Each new feature was covered by:

• unit and end-to-end tests,
• automatic validation of code quality in CI/CD pipelines,
• mutual code review between teams from Europe and the USA.

Compared to many projects where tests are only an addition, here they were an integral part of the process. Our specialist particularly appreciated the environment in which good practices were not only declared but also realistically implemented.

The project team operated in two time zones — in Poland and California — which required efficient organization and communication. In order to strengthen cooperation and better understand the specifics of the work of colleagues from overseas, our specialist conducted a three-week delegation to the client's office in the USA.

On site, he worked side by side with the American part of the team, participating in daily tasks, learning the realities of their work and improving joint processes. The result was better synchronization, greater trust and developed ways of communicating that were maintained after returning to remote work.

After the successful implementation of MVP, the project went into the development phase — new functions are added, existing elements are optimized, and the application becomes an increasingly key tool in the daily work of marketing and sales departments.

‍

Our specialist continues to participate in the work of the team — not only as a developer, but also as a person who supports the team in maintaining quality, sharing knowledge and developing good practices. His role with MVP has evolved into a stable support in the further stages of product development.