Table of contents
About the client
Österreichische Lotterien is the licensed national provider of gaming, betting, and entertainment products in Austria.
Since its founding in 1986, the company has offered a wide range of responsible services and products, including Lotto, EuroMillions, and various others.
Committed to integrity and social responsibility, the company acts as a key partner for Austrian sports and social institutions, directing a significant portion of its revenue toward public benefit initiatives.
Business challenge
Österreichische Lotterien was in the final phase of a strategic project to modernise its online gaming platform, make it more user-friendly and accessible, and enhance digital sales. However, the initiative had stalled.
The client needed a reliable technology partner to take ownership of the project’s completion. They were looking for an effective team that could not only deliver the required technical work but also integrate seamlessly with their internal processes.
Having previously worked with Österreichische Lotterien’s products, we were the perfect partner to finish the task and deliver the remaining part of the project, connected with core titles like Bingo, Lucky Day, Zahlenlotto, Toto & Torwette, and Joker.
Previously, we had refactored the existing foundation to align it with the company’s coding standards, implemented a dedicated testing environment, and thoroughly validated its functionality. Our strong understanding of the client’s environment allowed us to adapt quickly to new requirements.
Establishing trust through preparation and scaling up for the final phase of the project
Our engagement began earlier – with a foundational task that allowed us to get to know the client’s environment and build confidence.
An initial team from Future Processing was brought on to help finalise a unified library of web components. This involved writing extensive test scenarios, extending the client’s existing testing framework, and developing React wrappers and adapters to ensure the new components could be integrated into the live platform with minimal disruption.
This preparation ensured consistent standards and tools, enabling today’s smooth development of new features.
When the time came to scale up for the final phase of the redesign project, Österreichische Lotterien took a big step by engaging us as a fully external, managed team.
They were clear about their expectations: they needed a versatile and autonomous team that could handle every aspect of the project, from frontend to backend.
Strengthening delivery with a quality-first approach
A key part of delivering value from the start is our proactive approach to quality.
For example, when an unfinished feature was unintentionally deployed to production, it caused cache refresh issues across several projects. The problem was quickly identified and we supported the investigation. Following a retro meeting, we introduced post-release checks to further ensure production stability.
In separate Bingo-related releases, our team quickly identified and reported issues such as an unfinished visual element and a layout bug, which enabled their prompt removal from production before they could affect customers.
This commitment to quality extended across the project. With Bingo, the initial scope and deliverables turned out to be ambitious and complex, which naturally created challenges in managing timelines. We worked closely with the business and UX teams to break the work into smaller, more manageable deliverables, clarifying acceptance criteria and unblocking inputs together with data owners.
When sprint goals evolved during delivery, we adapted our approach by improving backlog grooming, sharpening planning, and introducing brief mid-sprint syncs during daily catch-ups to review progress toward the Sprint Goal and adjust priorities or resources as needed to increase transparency and alignment.
At the same time, multiple features for products such as EuroDreams, Bingo, and TOTO & Torwette were being developed in parallel, each with different approval cycles. To avoid conflicts, we adjusted prioritisation, refined backlog management and enhanced communication with the business team, preventing overlapping rollouts while keeping quality at the forefront.
Transforming the collaboration by removing bottlenecks through a value-driven BA role
As the relationship matured, we collaboratively identified opportunities to improve our working model. Historically, communication was managed through a single point of contact, which ensured control and consistency but often delayed clarifications. The introduction of a BA role added a complementary path that made discussions more efficient.
Our Business Analyst (BA) took a value-driven approach, focusing on delivering exceptionally clear analyses, asking insightful questions in advance of meetings, and proving how direct communication could lead to fewer errors and faster clarifications.
Within a month, we jointly recognised the value of enabling direct communication between the BA, the Product Owner, and business stakeholders. This was a turning point. It transformed the workflow from a linear, intermediated process into a collaborative partnership.
The BA became the “first line of contact” for developers on requirement-related questions, and the direct link to the business for clarifications. This change significantly accelerated the development cycle and reduced the risk of misinterpretation.
By focusing on delivery, demonstrating proactive ownership, and collaboratively refining our processes, solidified our position as a trusted partner. The client’s satisfaction was reflected in the team’s growing responsibilities and the success of the project.
Benefits of our collaboration
- Ensured project stability and knowledge retention with zero team rotation and over 90% team availability maintained over a critical six-month period
- Predictability and quality improved through multi-layered verification, refined sprint planning and backlog grooming
- Mitigated business risk by proactively identifying and resolving a critical production incident before it impacted end-users
- Reduced development friction and ensured consistent user experience by leveraging a single library of web components previously tested by our team in a previous project
- Increased efficiency as rising team velocity enabled more accurate planning and faster delivery cycles
- Collaboration enhanced by introducing a BA model that removed bottlenecks, cut requirement errors and accelerated feature delivery
Technologies used
