This document describes the product development process used by the SPORT APP team. The process is organized by missions which have defined key performance indicators. The team generates hypotheses for each mission, prioritizes them, then shapes and builds the top hypotheses into user stories. They measure data from the app to see if it validates the hypotheses and learn insights to apply to future versions. The goal is to test ideas quickly, understand user behavior, and use data to continuously improve the app.

1. SPORT
Small Bets: Hypotheses & Data
Ryan Hewitt

2. SPORT APP
SQUAD
Engineering UX
Product Owner
BAQA
PMTech Lead
APP

3. SPORT APP
ORGANISED BY MISSIONS
Jan - Apr ‘16
Get millions of fans to personalise the app & stay
updated on their favourite sports
BA role
• Define 3 KPIs per mission
• Target & progress (2 million push alert subscribers)

4. SPORT APP
GENERATE HYPOTHESES

5. SPORT APP
GENERATE HYPOTHESES
• Ideas for the mission
• Lo fidelity designs, data, competitors

6. SPORT APP
PRIORITISATION
• BA led session
• Relative score for each
hypothesis
• Select top 5 for BA to
shape

7. SPORT APP
PRODUCT SHAPING
• Break work into user stories
• Requirements & AC’s > 3 Amigos

8. SPORT APP
BUILD
• Support: the development team
• Confirm: demo, guerrilla testing,
user testing
• Release: staged rollouts, feature
switches, no release trains

9. SPORT APP
MEASURE
• BA reviews data & progress
• Chartbeat, dax, user reviews,
A/B testing, surveys
• Actuals vs hypothesis
• Visualise data
• Realtime dashboard, physical board, daily emails

10. SPORT APP
LEARN
BML session every 2 weeks
• BA presents latest stats
• Insights: user behaviour vs expected
• Actions: v2, v1, pivot, adjust our hypotheses/goals

11. SPORT APP
• Missions & KPIs: Convey the why & understand success
• Hypotheses: Testable ideas & forecast value. Prioritised
• Shape & Build: User stories & release quickly
• Measure & Learn: data to validate hypotheses & make
decisions
LIFECYCLE SUMMARY

12. SPORT APP
Questions?
Fin.