Software & Technical Project Delivery

Ava Media

Multi-platform software delivery across Web, Mobile, and Smart TV.

Coordinated delivery across engineering, QA, external partners, and stakeholders for a digital product serving more than 50,000 users.

WebMobileSmart TVScrumQA / UATAPI Integrations
50K+

Users

6

Engineers

~15

Contributors

6–8

API / Integration Dependencies

The Challenge

Coordinating delivery across platforms, teams, and technical dependencies.

Ava Media was a multi-platform digital product spanning Web, Mobile, and Smart TV. Delivery involved approximately 15 contributors, including 6 engineers, 1–3 QA resources, and approximately 3 external partners.

The delivery environment also included approximately 6–8 API and integration dependencies. Keeping releases, testing, priorities, dependencies, and stakeholder expectations aligned was a central part of the project coordination.

My Role

Coordinating technical delivery from development through live production.

My focus was keeping the different parts of the delivery process connected: engineering work, QA, releases, dependencies, external partners, and stakeholder priorities.

Release Sequencing

Coordinated release sequencing across multiple platforms while aligning engineering, QA, and external dependencies.

QA & UAT

Coordinated QA and UAT activities, helping the team identify blockers, clarify priorities, and prepare releases for production.

Dependencies & Blockers

Tracked dependencies across internal teams, external partners, and approximately 6–8 API or integration touchpoints.

Stakeholder Alignment

Kept engineering, QA, partners, and stakeholders aligned around changing priorities, delivery decisions, and production needs.

Delivery Model

The delivery approach evolved with the product lifecycle.

During active development, the team worked in a Scrum-style model. Once the product moved into live production, the workflow shifted toward a Kanban-style approach focused on ongoing delivery and stabilization.

Development

Scrum-style Delivery

Coordinated development work, priorities, engineering, QA, and stakeholder alignment through structured delivery cycles.

Live Production

Kanban-style Workflow

Supported continuous prioritization, live issues, dependencies, production needs, and post-release stabilization.

Product Ecosystem

A multi-platform product with multiple technical touchpoints.

Web
Mobile
Smart TV
6 Engineers
1–3 QA
~3 External Partners
6–8 API / Integration Dependencies
50K+ Users
Outcome

Supported delivery of a live multi-platform product serving 50K+ users.

The project progressed from active development into live production, with the delivery approach adapting to the needs of ongoing releases, operational issues, dependencies, and post-release stabilization.

50K+

Users supported across the product ecosystem

3

Major platforms: Web, Mobile, and Smart TV

~15

Contributors across the delivery environment

What I Learned

Delivery management is about keeping the whole system moving.

Multi-platform delivery requires active dependency management across technical boundaries, not just within an individual engineering team.

Release sequencing becomes increasingly important when multiple platforms and external dependencies need to move together.

The delivery model can evolve with the product, from structured development cycles to a more continuous production and stabilization workflow.