FOX PLAY SCRUM CYCLE

AUTOMATED WORKFLOW (STAGE 1)

DEMAND
MANAGEMENT

PRODUCT LIFE CYCLE

ROADMAP
Workshop

DEC

Scrum
XP
LEAN
ITIL

Consulting & Coaching

JAN

FEB

APR

MAY

Demand Management
Backlog Creation & Grooming

Multi-Project Management
(Strategic Demand: Portfolio Backlog)

Business Flows
Services / Operations (Stories)
Acceptance Criteria / Scenarios

Bug/Issues Management
(Operative Demand)

Scrum Framework (workflows)

Product Life cycle

TEAM

MAR

!
!

Services Catalogue
(Architecture & Management)

PERFORMANCE TEAM

PRODUCT LIFE CYCLE

ROADMAP

Consulting & Coaching

JUN

JUL

AGO

SEP

Capacity Management
(Productivity Based on Value Delivery)
Services Level Management:
SLA Definition
SLO (Operative)
Underpinning Contract (with Vendors)

PERFORMANCE TEAM

OCT

NOV

Balance Scorecard:
Value Proposition (Measured)

Business Model Canvas

Gamified Product Techniques:
How to build an Addictive Product for the
audience.

HIGH PERFORMANCE TEAM

PRODUCT LIFE CYCLE

Feedback

Emergent
Opportunities

Portfolio Backlog
(Projects)

Budget
(Resources)

FOX Play

FOX Play

FOX Sports

FOX Sports

Nat Geo Play

Nat Geo Play

Allocation

etc.

communicate

eval.

etc

communicate

Product 1

Product 2

Product 3

FOX PLAY

FOX Sports

Nat Geo Play

Feedback

MULTI-PRODUCT SCENARIO: ADAPTIVE PORTFOLIO MANAGEMENT

FOX PLAY

SCRUM CYCLE
& KEY ROLES

FOX PLAY: SCRUM KEY ROLES

KEY RESPONSIBILITIES + STAKEHOLDERS

PO

SM

3P

Client

Product Owner

Scrum Master

Dev Team

3PP Partners

Interfaces
between business &
dev. team. Facilitates
the backlog grooming
instance

Facilitates
& Coordines Team work
to-do during the Sprint

Analyze, Develops and

Test Features (Stories)

Analyze, Develops and

Test Features (Stories)

DER (UX)
+
RICCI (UX)

MONTAGNESE (UX)

(UX) TEAM
+
(UX) PARTNERS
(INSITE, ORIGIN,
ETC)

OTHER PARTNERS
(Accedo, Toolbox,
etc)

Roles
Generates input
(end-users, customers,
clients, internal /
external team and
others). Validates
Features developed

Stakeholders
(Teams)

PROD-LAT
PROD-BR
URM
MKT
UX
CUSTOMERS
3PP

ROSALES (UX)

!!

FOX PLAY: SCRUM CYCLE

ARTIFACTS + KEY ROLES

(5) Daily Meeting

T

SM

Every day: 15 minutes

Key Roles:
(PO) Product Owner

SM

PO

24h

(6) Sprint
Review / Demo

(T) Team

Day 9

(0) Input from

(SM) Scrum Master

(C) Client

End-Users, Customers, Clients,

Team and Other Stakeholders
T

SM

PO

(7) Sprint
Retrospective
Kaizen
Day 10

PO

Sprint
10 Work Days

Sprint 3
Sprint 2
SM

PO

Sprint 1

(1) Backlog
Grooming

(2) Product
Backlog

(3) Sprint
Planning

(4) Sprint
Backlog

(Feature
Description)

(Features
Prioritized)

Day 1: (2 - 3h)

(User Stories)

Customer Ready

(8) Incremental Product Release

WHY WE USE

USER STORIES?

USER STORIES

USER CENTRIC APPROACH

In 1973 Paul McCartney was

interviewed and asked about why
The Beatles songs were so
amazingly popular.
One of his responses was that
their songs were among the
first to use a lot of pronouns.
His point was that these
helped people more closely
identify with their songs.

USER STORIES
BASIC STRUCTURE

!
!
!
!
!
!

As a <type of user>, I want <some goal> so that <some benefit>

USER STORIES
BASIC STRUCTURE

!
!
!
!
!
!
!
!
!
!
!
!

Business Value

As a <type of user>, I want <some goal> so that <some benefit>

Acceptance Criteria:
When I <perform an action>, I expect <a reaction>

USER STORIES

USER CENTRIC APPROACH

As DEV I need integrate New

Relic as a monitoring tool in
order to monitor platform
performance in real time

!
As Marketing I need to embed
FOX Play Videos at Twitter in
order to increase video starts

!
As a FOX Play Basic User
I need a Trial option for try the
Premium tier

!
As PROD-BRA I need to add a
subtitles option for the final user

!
As PROD-LATAM I need to restrict
access to some Live Events in Chile, only
for FOX Sports Premium Subscribers, in
order to motivate the Sports Package
subscription.

!
As PROD-BRA I need to create
syndication feeds, in order to
share feeds with third parties and
increase video starts.

USER STORIES

FROM REQUIREMENTS TO FUNCTIONALITY (DOCUMENTED)

REQUIREMENT

FUNCTIONALITY

As Marketing I need to
embed FOX Play Videos at
Twitter timeline in order to
increase video starts

USER STORIES
IN BACKLOG

SERVICES &
OPERATIONS
IN CATALOGUE

USER STORIES

STORIES CREATION AT JIRA:

(1) Project:
FOXPLAYLatam (FOXL)

(2) Issue Type:

Story

(3) Summary:
Story Title

(4) FOX Reporter Team:

PROD-LAT, PROD-BR,
URM, or UX-IT

(5) Description
Story Description +
Acceptance Criteria

(6) Epic Link

url.foxites.com/jira

Epic Related
(Optional Field)

USER STORIES

STORIES EDITION AT JIRA: BASIC FIELDS

Jira ID

FOX Reporter Team

USER STORIES

STORIES EDITION AT JIRA: BASIC FIELDS

Status: In progress

Type
Epic
Story
Task

Watch Issue

Blocked

Done etc

PRODUCT BACKLOG

GROOMING & DEVELOPMENT

FOX PLAY: SCRUM CYCLE

PRODUCT BACKLOG CREATION

C
C

PROD-LAT

PROD-BRA

UX-IT

URM

url.foxites.com/
backloglatam

url.foxites.com/
backlogbrasil

url.foxites.com/
backlogux

url.foxites.com/
backlogurm

PRODUCT
BACKLOG
url.foxites.co
m/backlogpo

FOX PLAY: SCRUM CYCLE

PRODUCT BACKLOG PROD-LAT

PROD-LAT
url.foxites.com/
backloglatam

FOX PLAY: SCRUM CYCLE

PRODUCT BACKLOG PROD-BRA

PROD-BRA
url.foxites.com/
backlogbrasil

FOX PLAY: SCRUM CYCLE

PRODUCT BACKLOG PROD-UX-IT

UX-IT
url.foxites.com/
backlogux

FOX PLAY: SCRUM CYCLE

PRODUCT BACKLOG URM

URM
url.foxites.com/
backlogurm

FOX PLAY: SCRUM CYCLE

PRODUCT BACKLOG (PO)

PRODUCT
BACKLOG
url.foxites.com/
backlogpo

FOX PLAY: SCRUM CYCLE

STORIES IN DEVELOPMENT

STORIES IN DEV
url.foxites.com/
jiradev

JIRA LIVE DEMO

FOX PLAY: SCRUM CYCLE

GROOMING & DEVELOPMENT INSTANCES

Ready!
C

PO

SM PO

(1) Input from

End-Users,
Customers,
Clients, Team
and Other
Stakeholders

(2) Backlog
Prioritization
Stories
Prioritization

(3) Illustration
Stories
Description

(4) Needs to
be Broken
Split Epics
and Add
Acceptance
Criteria (AC)

REQUIREMENTS at JIRA

(5) Ready for

Planning
Stories well
illustrated that
includes AC

(6) Selected
for Dev
Candidate
Stories

SM
C

SM

(6) To-Do
Stories
Candidate
Stories

(7) In
Progress

PO

(8) In QA

(9) Blocked

DEVELOPMENT Instances at JIRA

(10) Done

FOX PLAY: SCRUM CYCLE

GROOMING & DEVELOPMENT INSTANCES
REQUIREMENTS

DEVELOPMENT

Backlog

Sprint

Stage

Instance

(1)
Backlog
Generation

(2)

(3)

(4)

Product Owners Grooming

(5)

(6)

(7)

(8)

(9)

(10)

Ready for Planning Meeting

Sprint
Backlog

Daily

Daily

Daily

Review /
Demo

JIRA
Status

New
Requirement

Prioritized

to be
Illustrated
with the
(PO)

Needs to
be broken

Ready for Planning

Selected for
Development
(Ready
for Dev)

In Progress

Blocked

in QA

Done

Key
Actions

(C) & (PO)

Create Epics

(C) & (PO)

Prioritize
Stories

(C) & (PO)

Illustrate
Stories

(C) & (PO)

+ (T)
Split Stories

(PO) Explain User Stories to the

Team

(T) Takes
Stories for
Development

(T)
Develops
User Stories

(T) Warns
about
roadblocks

(T)
Prepare
and Run
Tests

(SM) + (PO)
Shows
stories done
to (C)

(C) & (PO)

Create Stories

(C) & (PO)

Split Epics
under covered
as Stories

(SM)
Coordinates
& Facilitates
Work
during
sprint

(SM) + (T)
Eliminates
roadblocks.

(C) & (PO)

Adds
Acceptance
Criteria

(C) & (PO) Discard Stories

(SM) + (T) Identify tasks, and

estimates size & eort (hours)

(SM) + (T) Identify stories not

ready

PRODUCT LIFE CYCLE

CURRENT PROGRESS

FOX PLAY: PRODUCT LIFE CYCLE

PROGRESS (FROM DEC 2014 to MARCH 2014)

100

PRODUCT OWNER DEFINITION

40%

PRODUCT BACKLOG CREATION

35%

USER STORIES CREATION

40%

USER STORIES ACCEPTANCE CRITERIA

25%

USER STORIES SCENARIOS

5%

PRODUCT BACKLOG GROOMING PROCESS

35%

ESTIMATIONS (SIZE + TIME)

25%

SCRUM WORKFLOW

35%

THE NEXT STOP IS

APR

MAY

JUN

JUL

SHORT TERM:

MID TERM:

JIRA Service Desk (Issues Management: Web Portal

Develop the Product Owners Network

+ e-mail reporting). Buggy = R.I.P.

Minimize Maintenance Project. Start planning

Apps Scrum Workflow Consolidation &

and tracking change requests & issues

Weekly Sync (FOX Play Web + FOX Play

Apps)

User Stories: Add Technical Stories & Team

Services Catalogue (Operations Inventory)

Development Stories

User Stories: Add Scenarios

Portfolio Backlog: (FOX Sports, Authentication 3.0,

Evergent, etc)

SCRUM FRAMEWORK
PREMISES & BENEFITS
PREMISES:

Incremental and organic product development, focused on business value delivery

Focus on team interaction over processes
Focus on generate collaboration with the client over agreement negotiation & struggle
BENEFITS:

Dynamic response to change (over following a long-term plan)

Direction over control
Self-management (Team empowerment)
"Kaizen": continuous improvement (on the product and the team)
Reduce time to market
Risk management
Incidents reduction (bugs)
Knowledge Management

Q&A

Thank You!