DEMAND MANAGEMENT

FOX PLAY SCRUM CYCLE AUTOMATED WORKFLOW (STAGE 1)

Workshop Consulting & Coaching

DEC JAN FEB MAR APR MAY+

TEAM PERFORMANCE TEAM

Scrum XP LEAN ITIL

Demand ManagementBacklog Creation & Grooming !Business FlowsServices / Operations (Stories)Acceptance Criteria / ScenariosScrum Framework (workflows)Product Life cycle

Multi-Project Management (Strategic Demand: Portfolio Backlog) !Bug/Issues Management (Operative Demand) !Services Catalogue (Architecture & Management)

PRODUCT LIFE CYCLEROADMAP

Consulting & Coaching

HIGH PERFORMANCE TEAMPERFORMANCE TEAM

JUL AGO SEP OCT NOVJUN

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

Balance Scorecard: Value Proposition (Measured) Business Model Canvas !Gamified Product Techniques:How to build an Addictive Product for the audience.

PRODUCT LIFE CYCLEROADMAP

Product 1

FOX PLAY

Emergent Opportunities

Budget (Resources)

Allocationetc.

FOX Play

FOX Sports

Nat Geo Play

etc

FOX Play

FOX Sports

Nat Geo Play

Portfolio Backlog (Projects)

Product 2

FOX SportsProduct 3

Nat Geo Play

eval.

PRODUCT LIFE CYCLEMULTI-PRODUCT SCENARIO: ADAPTIVE PORTFOLIO MANAGEMENT

communicate communicate

Fee

db

ack

Fee

db

ack

FOX PLAY SCRUM CYCLE & KEY ROLES

FOX PLAY: SCRUM KEY ROLESKEY RESPONSIBILITIES + STAKEHOLDERS

CClient

Generates input (end-users, customers,

clients, internal / external team and others). Validates

Features developed

PO Product Owner

Interfaces between business & dev. team. Facilitates

the backlog grooming instance

SMScrum Master

Facilitates & Coordines Team work to-do during the Sprint !!

TDev Team

Analyze, Develops and Test Features (Stories)

3P3PP Partners

Analyze, Develops and Test Features (Stories)

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

MONTAGNESE (UX) (UX) TEAM +

(UX) PARTNERS (INSITE, ORIGIN,

ETC)

DER (UX) +

RICCI (UX)

Roles

Stakeholders (Teams)

OTHER PARTNERS (Accedo, Toolbox,

etc)

ROSALES (UX)

(0) Input from End-Users, Customers, Clients, Team and Other Stakeholders

(2) Product Backlog (Features Prioritized)

(4) Sprint Backlog (User Stories)

(1) Backlog Grooming (Feature Description)

Sprint 10 Work Days

(8) Incremental Product Release

(5) Daily Meeting Every day: 15 minutes

(6) Sprint Review / Demo Day 9

(7) Sprint Retrospective Kaizen Day 10

Customer Ready

PO

T SM

24hC T SM PO

T SM PO

T SM PO

(SM) Scrum Master

(T) Team

(PO) Product Owner

(C) Client

Key Roles:

Sprint 1

Sprint 2

Sprint 3

FOX PLAY: SCRUM CYCLEARTIFACTS + KEY ROLES

(3) Sprint Planning Day 1: (2 - 3h)

WHY WE USE USER STORIES?

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.

In 1973 Paul McCartney was interviewed and asked about why The Beatles songs were so amazingly popular.

USER STORIESUSER CENTRIC APPROACH

!!!!!!As a , I want so that

USER STORIESBASIC STRUCTURE

!!!!!!

!!!!!!As a , I want so that

USER STORIESBASIC STRUCTURE

Business Value

Acceptance Criteria:When I , I expect

!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 Marketing I need to embed FOX Play Videos at Twitter in order to increase video starts

!As DEV I need integrate New Relic as a monitoring tool in order to monitor platform performance in real time

!As a FOX Play Basic UserI 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-BRA I need to create syndication feeds, in order to share feeds with third parties and increase video starts.

USER STORIESUSER CENTRIC APPROACH

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

C

USER STORIES IN BACKLOG

SERVICES & OPERATIONS

IN CATALOGUE

REQUIREMENT FUNCTIONALITY

USER STORIESFROM REQUIREMENTS TO FUNCTIONALITY (DOCUMENTED)

USER STORIESSTORIES 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 Epic Related (Optional Field)

!

url.foxites.com/jira

USER STORIESSTORIES EDITION AT JIRA: BASIC FIELDS

Jira ID

FOX Reporter Team

USER STORIESSTORIES EDITION AT JIRA: BASIC FIELDS

Watch Issue

Epic

Story

Task

Type

Status: In progress Blocked Done etc

PRODUCT BACKLOG GROOMING & DEVELOPMENT

PROD-LAT url.foxites.com/backloglatam

FOX PLAY: SCRUM CYCLEPRODUCT BACKLOG CREATION

PROD-BRA url.foxites.com/backlogbrasil

UX-IT url.foxites.com/backlogux

URM url.foxites.com/backlogurm

PRODUCT BACKLOG url.foxites.com/backlogpo

C

CC

C

FOX PLAY: SCRUM CYCLEPRODUCT BACKLOG PROD-LAT

PROD-LAT url.foxites.com/backloglatam

FOX PLAY: SCRUM CYCLEPRODUCT BACKLOG PROD-BRA

PROD-BRA url.foxites.com/backlogbrasil

FOX PLAY: SCRUM CYCLEPRODUCT BACKLOG PROD-UX-IT

UX-IT url.foxites.com/backlogux

FOX PLAY: SCRUM CYCLEPRODUCT BACKLOG URM

URM url.foxites.com/backlogurm

FOX PLAY: SCRUM CYCLEPRODUCT BACKLOG (PO)

PRODUCT BACKLOG url.foxites.com/backlogpo

FOX PLAY: SCRUM CYCLESTORIES IN DEVELOPMENT

STORIES IN DEV url.foxites.com/jiradev

JIRA LIVE DEMO

T T C T PO

T T

T SM

T SM

(5) Ready for Planning Stories well illustrated that includes AC

DEVELOPMENT Instances at JIRAREQUIREMENTS at JIRA

(3) Illustration Stories Description

(6) Selected for Dev Candidate Stories

T SM POC

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

(2) Backlog Prioritization Stories Prioritization

C T PO

(1) Input from End-Users, Customers, Clients, Team and Other Stakeholders

FOX PLAY: SCRUM CYCLEGROOMING & DEVELOPMENT INSTANCES

(7) In Progress

(8) In QA (9) Blocked (10) Done (6) To-Do Stories Candidate Stories

Ready!

FOX PLAY: SCRUM CYCLEGROOMING & DEVELOPMENT INSTANCES

StageREQUIREMENTS DEVELOPMENT

Backlog Sprint

Instance (1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

Backlog Generation Product Owners Grooming 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

(C) & (PO) Adds

Acceptance Criteria

(SM) + (T) Identify tasks, and estimates size & eort (hours)

(SM) Coordinates & Facilitates

Work during sprint

(SM) + (T) Eliminates

roadblocks.

(C) & (PO) Discard Stories (SM) + (T) Identify stories not ready

PRODUCT LIFE CYCLE CURRENT PROGRESS

FOX PLAY: PRODUCT LIFE CYCLEPROGRESS (FROM DEC 2014 to MARCH 2014)

USER STORIES ACCEPTANCE CRITERIA 25%

5%

PRODUCT OWNER DEFINITION 40%

PRODUCT BACKLOG CREATION 35%

40%USER STORIES CREATION

35%

ESTIMATIONS (SIZE + TIME) 25%

1000

SCRUM WORKFLOW 35%

USER STORIES SCENARIOS

PRODUCT BACKLOG GROOMING PROCESS

SHORT TERM: ! JIRA Service Desk (Issues Management: Web Portal

+ e-mail reporting). Buggy = R.I.P. Minimize Maintenance Project. Start planning

and tracking change requests & issues User Stories: Add Technical Stories & Team

Development Stories User Stories: Add Scenarios Portfolio Backlog: (FOX Sports, Authentication 3.0,

Evergent, etc) !

THE NEXT STOP IS

APR MAY JUN JUL

MID TERM: ! Develop the Product Owners Network

Apps Scrum Workflow Consolidation & Weekly Sync (FOX Play Web + FOX Play Apps)

Services Catalogue (Operations Inventory)

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

SCRUM FRAMEWORKPREMISES & BENEFITS

Q&A

Thank You!