Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Project Las VegasOperational Reporting-Release Planning meetingAugust 18, 2009                                            ...
Operational Reporting-  Release Planning Meeting  • Stakeholders identification  • Cross-Functional Core Team- Roles & Res...
Operational Reporting-  Stakeholders identification  • Role- Business QA (Chris Benson)  • Role- Data Stitching Specialist...
Cross-Functional Core Team-  Roles & Responsibilities      #             Suggested Person                               Ro...
Operational Reporting-  Steps to get to “Merchandizing”  Create                                    Set Up                 ...
Operational Reporting-  High Level Scope  Merchandizing Reporting deals with-  What – Merchandizing, Products, SKUs, Bundl...
Operational Reporting-  Exact Scope for next 6 weeks  • The following questions will define the scope for Release 1.2:    ...
Operational Reporting-  Process        – Product owner guards scope               • Uses (existing) intake process to avoi...
Operational Reporting-  (Suggested) Release Plan  • Sprint 0 Plan (2 weeks starting 8/24)        – Modeling the platform (...
Thank You!SYMANTEC PROPRIETARY/CONFIDENTIAL – INTERNAL USE ONLYCopyright © 2009 Symantec Corporation. All rights reserved.
Upcoming SlideShare
Loading in …5
×

ECommerce Merchandizing Operational Reporting- release planning meeting- draft

713 views

Published on

Release Planning for Ecommerce Merchandizing related operational reporting based on Enterprise Data Warehousing & Enterprise Web Analytics. Cross-functional "transient" team led by me to deal with operations related data issues.

Published in: Business
  • Be the first to comment

  • Be the first to like this

ECommerce Merchandizing Operational Reporting- release planning meeting- draft

  1. 1. Project Las VegasOperational Reporting-Release Planning meetingAugust 18, 2009 INTERNAL USE ONLY SYMANTEC PROPRIETARY/CONFIDENTIAL Copyright © 2009 Symantec Corporation. All rights reserved.
  2. 2. 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 happenSYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved. 2
  3. 3. 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)SYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved. 3
  4. 4. Cross-Functional Core Team- Roles & Responsibilities # Suggested Person Role Responsibility Accepted • Review & prioritize sprint backlog 1 Lyn Tran Product Owner  • Guard scope for current sprint • Define sprint backlog item 2 Cresentia Sparrow-Lobo SME  • Assist product owner in prioritization • Define sprint backlog item 3 Robert Neil SME  • Assist product owner in prioritization • Define sprint backlog item 4 Swapnil Mahajan SME  • Assist product owner in prioritization • Articulates the sprint backlog item 5 Arvind Sathyamoorthy Primary SME  • Collaborates with Architects/dev Primary stakeholder • Describe sprint backlog items 6 Chris Benson  (THE user) • Accept or reject sprint results • Implements the sprint backlog item 7 Suryam Kurma Dev Lead  • Collaborates with dev/QA/users 8 Ravi Tadwalkar Scrum Master • Facilitator role  9 Samy Client Sponsor • Collaborates with product owner SYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved. 4
  5. 5. Operational Reporting- Steps to get to “Merchandizing” Create Set Up Assign to Virtual Merchandize • Products • Merchandizing Catalog • What – Products, • Bundles Relationships • Products Bundles, Prices • Pricing • Bundles • Where – Pages and Slots • Who – Sub Channels, Vendors • When – Start and End Dates Master Catalog Virtual CatalogSYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved. 5
  6. 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 monitoringSYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved. 6
  7. 7. 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 ReportSYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved. 7
  8. 8. Operational Reporting- Process – 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. 8
  9. 9. Operational Reporting- (Suggested) Release Plan • 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 happenSYMANTEC PROPRIETARY/CONFIDENTIAL. Copyright © 2009 Symantec Corporation. All rights reserved. 9
  10. 10. Thank You!SYMANTEC PROPRIETARY/CONFIDENTIAL – INTERNAL USE ONLYCopyright © 2009 Symantec Corporation. All rights reserved.

×