A Multi-Tenant Micro-Frontend Kubernetes Web App

For a Reliable Video Streaming Platform

USA

LOCATION

Live Entertainment

INDUSTRY

Scope Estimate

Service Provided

01. The CLIENT

About the Client

BUSINESS

Our client request was from an entertainment startup aiming to transform online streaming with interactive features inspired by applied gamification techniques.

BACKGROUND

They wanted an estimate for their vision for a web app embeddable into poker video streaming platforms that would improve viewer engagement.

02. The Project Challenge

INITIAL REQUEST

As the client’s initial vision was focused on the front end features, so they relied on Maven Solutions to evaluate the needs for the backend architecture with scalability to support their vision from the MVP to a scalable product.

THE CHALLENGE

The Maven Solutions team has presented clarification and technical options. A video stream embeddable web app was only the first phase of the product development. Eventually, a standalone platform do the opposite would be needed, meaning it would need to have the capability to embed streams onto the platform.

The client sought a solution that would:

01

Seamlessly embed into existing video streaming platforms, without image or sound lag

02

Have the potential to grow from an app add-on to existing streaming services into a fully functional streaming platform

03

Allow interactive feature experimentation capabilities for product feature A/B testing BI analytics

03. The SOLUTION

PROJECT SOLUTION

Our Strategic Approach

The technical solution was to apply the micro frontend approach that would keep the backend as microservices while the frontend would be developed as an embeddable microfrontend. This technical solution would allow to reuse components and the design system to expand the MVP into a fully functional platform around the initial core solution.

To organize the development process, Maven Solutions has offered to use the Disciplined Agile Delivery method:
1.Three project phases: Inception, Construction, Transition
2. The freedom to choose any appropriate processes and methodology
3. A combination of Agile and classic project management approaches
4. The focus on the business value of each delivery, not just on development processes

Inception steps and timeline

We offered to map the product vision with steps, timelines, and resources needed to achieve them. The proposed 6-week Inception stage helped define the architecture on week one, explore product scope in three one-week sprints, and form release teams to deliver the release plan.

deliverables

The list of actionable deliverables available after the Inception phase would include Product Development Roadmap; detailed Functional and infrastructure architecture charts; Functional requirements broken down to Components, Epics, and User Stories; User Stories containing acceptance criteria and visual implementation guidelines/design reference; Test strategy documentation; Infrastructure and team proposals for MVP Construction and Transition phases.

Outcomes

The Inception phase would enable the outcomes necessary for the client to plan market testing and to budget reliably. Product development phases would be fully defined, the scope of the MVP would be crystal clear and it would be optimal for time-to-market, all the resource needs would be clear and ready to deploy.

Building and Scaling

Maven Solutions has outlined the timelines and activities for the Construction and the Transition Phases, defining the process of delivering the Concept, the Prototype, the MVP, and steps needed for product scaling.

Planning with Confidence

Maven Solutions applies Stacey’s Project Uncertainty Model so that requirements and project technology challenges do not negatively impact product development. Because the project was evaluated to be Complex (with a vision, but unclear scope around features) with 60% Budget evaluation accuracy, the Dedicated Team model was offered for the phases following Inception.

The Inception phase was evaluated from $4000 to $6000 depending on the options of scope packages to explore presented to the client

04. The Results

Value Delivered

Optimized Roadmap

Broke down the product vision into functional MVP, prototype, further product versions
Validated by all the necessary technology solutions
No need to wait for the "perfect" product at an undefined future date

Better Time-to-market

Shaved off at least 3 month from the original release estimate
A flexible product plan that's responsive to market signals
A framework to map feature releases to user satisfaction

Reduced Bottlenecks

Scalable, automated development environment
Staged, balanced work plan for visual design team from the prototyping stage
No heavy design workloads during late product stages

CTO

Video Streaming Startup

The approach proposed my Maven Solutions actually better served our business capabilities. Our original idea was to use iframes, but this would place severe constraints over functionality and technology options in the future. From the time-to-market perspective, the input by Maven Solutions has helped us to build a better product foundation.