Project Las Vegas

Operational Reporting-

Release Planning meeting

August 18, 2009 INTERNAL USE ONLY

SYMANTEC PROPRIETARY/CONFIDENTIAL Copyright © 2009 Symantec Corporation. All rights reserved.

SYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved.

Operational Reporting-

Release Planning Meeting

• Stakeholders identification

• Cross-Functional Core Team- Roles & Responsibilities

• Merchandizing Reporting

– High Level Scope- Steps to get there

• What we will not do for 1.2

– Overview

– Process

• Release Planning- scope (product backlog items, i.e. problem statements)

• Problem statement will be pattern style (name, problem, solution, consequences)

– (Suggested) Release Plan

• Sprint 0 Plan (2 weeks starting 8/24)

– (Canned) Report PoC in Operational universe

• Sprint 1 Plan (2 weeks)

– Operational universe design & canned reports

• Sprint 2 Plan (2 weeks)

– Preview universe design & canned reports

• Sprints will continue as product backlog updates happen

2

SYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved.

Operational Reporting-

Stakeholders identification

• Role- Business QA (Chris Benson)

• Role- Data Stitching Specialist (Angela Cearns)

• Role- Operations Specialist (Chantra C)

• Role- Solution Manager (Robert Neil)

3

SYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved.

# Suggested Person Role Responsibility Accepted

1 Lyn Tran Product Owner • Review & prioritize sprint backlog

• Guard scope for current sprint

2 Cresentia Sparrow-Lobo SME • Define sprint backlog item

• Assist product owner in prioritization

3 Robert Neil SME • Define sprint backlog item

• Assist product owner in prioritization

4 Swapnil Mahajan SME • Define sprint backlog item

• Assist product owner in prioritization

5 Arvind Sathyamoorthy Primary SME • Articulates the sprint backlog item

• Collaborates with Architects/dev

6 Chris Benson Primary stakeholder

(THE user)

• Describe sprint backlog items

• Accept or reject sprint results

7 Suryam Kurma Dev Lead • Implements the sprint backlog item

• Collaborates with dev/QA/users

8 Ravi Tadwalkar Scrum Master • Facilitator role

9 Samy Client Sponsor • Collaborates with product owner

4

Cross-Functional Core Team-

Roles & Responsibilities

SYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved.

5

Operational Reporting-

Steps to get to “Merchandizing”

Create

• Products

• Bundles

Set Up

• Merchandizing Relationships

• Pricing

Assign to Virtual Catalog

• Products

• Bundles

Merchandize

• What – Products, Bundles, Prices

• Where – Pages and Slots

• Who – Sub Channels, Vendors

• When – Start and End Dates

Master Catalog Virtual Catalog

SYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved.

6

Operational Reporting-

High Level Scope

Merchandizing Reporting deals with-

What – Merchandizing, Products, SKUs, Bundles & Pricelists

Where – Pages and Slots

Who – Sub Channels, Vendors

When – Start and End Dates

Merchandizing Reporting does not deal with-

• Site Setup

• Catalog management

• Content management

• Transactions- Orders & Refunds

• Performance monitoring/tuning

• Application monitoring

SYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved.

Operational Reporting-

Exact Scope for next 6 weeks

• The following questions will define the scope for Release 1.2:

– What target merchandise does not lead to a SKU/price?

– What SKUs are not included as incoming?

– What subscription SKUs are not available for sale?

– What is merchandised on certain product placement pages?

• The following will be decoupled from Operational reporting but still delivered in Release 1.2:

– Hourly Sales Report CODS

– Order Value Exception Report

7

SYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved.

Operational Reporting-

Process

8

– Product owner guards scope

• Uses (existing) intake process to avoid scope creep

– Review & prioritize sprint backlog

– Guard scope for current sprint

– Release Planning- scope

• product backlog items, i.e. problem statements

• Problem statement doc can be used for acceptance testing as well

– Problem statement will use pattern style documentation

• Name (to identify the problem statement),

• Problem (defined),

• Solution (approach/alternatives/trade-offs),

• Consequences (expected results)

SYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved.

Operational Reporting-

(Suggested) Release Plan

9

• Sprint 0 Plan (2 weeks starting 8/24)

– Modeling the platform (-based on APPS schema)

– (Canned) Report PoC in Operational universe

– User demo (validation of report PoC)

• Sprint 1 Plan (2 weeks)

– Operational Universe design (-based on APPS schema)

– canned reports

– User demo (validation of universe design)

• Sprint 2 Plan (2 weeks)

– PREVIEW universe design (-based on PREVIEW schema)

– canned reports

– User demo (validation of universe design)

• Sprints will continue as product backlog updates happen

SYMANTEC PROPRIETARY/CONFIDENTIAL – INTERNAL USE ONLY Copyright © 2009 Symantec Corporation. All rights reserved.

Thank You! Thank You! Thank You! Thank You! Thank You!