Fanatics Phase 1-MVP

2019 Scope, Requirements, Assumptions & Open Items

Fanatics SCOPE
- Scope
Fanatics - Scope Fanatics - Out of Scope Fanatics - Open Questions
Phase 1 - MVP
Item Ingestion
● KLINK support to automate Style and SKU creation if all attribute values are provided in advance.
● KLINK support for automatic publish to Kohls.com without manual intervention if data provided in
advance.
● KLINK support for mass upload images to an FTP server as part of product creation
Performance Scaling
● Scale performance of RMS, CMS and Image upload via Censhare to support additional load
● Scale performance of Solr
● Scale performance of existing DSCO and all Inventory/Order Management Feeds including Sales Hub
to downstream systems to accommodate additional SKUs and orders.
Phase 1 - MVP
● New Kohl’s internal sku id to be sent to DSCO (new process being asked).
● Fanatics unable to generate physical packslips. Confirmed New KT effort fo Returns not in scope k for
MVP. but need to manage Risk
● Fanatics unable to generate 3rdParty Bill. Confirmed New KT effort fo Returns not in scope k for MVP.
but need to manage Risk
● New KT effort for Returns confirmed not in Scope. Re-Confirm into Analytics
● How to flip DS indicator for fanatics items in CICS - Open Item
● Taxware code for all Fanatics items - Fanatics team to send pre-mapping
● DS team to update data in twebitem (e.g. shipping service code, ship alone, hazmat etc)
● Censhare Stories and Integration pending
● Legacy MDM and understanding of scaling, integration needs
Phase 2
● New Returns Process: A new technology solution to support a new Returns process for multiple SKUs
with the same UPC
● Item Ingestion: Ability to support ingesting an Item which has multiple SKUs with the same UPC
● Mass Review & Mass Maintenance Feature formalization - Based on lockdown with Business to take as
New program Scope, Funding and Timeline confirmation
● Automation of Custom CP Creation
● Support Multi sku to one UPC (one UPC for multiple vendors)
Phase 1 - MVP
● Mass Review & Mass Maintenance: This was not part of the original requirements/estimate.
● Automation of Custom CP Creation
● New Returns Process: A new technology solution to support a new Returns process for multiple SKUs
with the same UPC.
● Returns confirmed not in Scope
● Will only be supporting Unique SKU. No duplication of Nike, In Store SKU
● Item Ingestion: Ability to support ingesting an Item which has multiple SKUs with the same UPC
Fanatics Phase 2 - Out of Scope
Fanatics Phase 2 - Open Questions TBD
TBD
MVP – Phase 1 Program Timelines for all Teams
Fanatics SCOPE
- Milestones
Scope Requirement/
Scope Dev Design Story Sign off Dev In Take Dev Completion QA, Perf
Completion UAT Production
MVP - Phase - 1
● Item Ingestion
● Performance Scaling
● Inventory/Order Management Feeds including Sales Hub
7/19 - orig 7/26 - -change ETA 8/02 -change ETA 8/09 -change ETA 8/30 - new ETA
Phase - 2
● New Returns, RTV Process
● Item Ingestion -for items that have multiple SKUs with the same UPC
● Mass Review & Mass Maintenance Feature
● Support one UPC for multiple vendors
3/15 - 0%
3/29 - 0%
4/05 - 0%
4/05 - 0%
5/31 - orig
6/14 - orig
7/05 - orig 3/22 - 0%
4/12 - 75%
4/12 - 15%
4/12 - 15%
6/7 -change ETA
6/21 -change ETA
7/12 -change ETA 3/29 - 10%
4/26 - to be 100%
4/26 - to be 100%
4/26 - to be 100%
6/14 -change ETA
6/28 -change ETA
7/19 -change ETA 4/5 - 20%
6/21 -change ETA
7/05 -change ETA
7/26 -change ETA 4/12 - 75%
6/28 - new ETA
7/12 - new ETA
8/02 - new ETA
5/31 6/14 6/28 6/28 8/30 09/19 10/03 10/25
Fanatics KEY MILESTONES
- Overall Milestone
MAR APR MAY JUN JUL AUG SEP OCT
DEV DESIGN 4/26
QA, PERF COMPLETION 7/12
DEV INTAKE

DEV COMPLETION 6/28

1
UAT
4/26
8/2
e sah
PSTORY SIGN OFF
4/26PRODUCTION
8/23
REQUIREMENT/SCOPE 4/19
NOT STARTED AT RISK / ISSUE ON TRACK COMPLETED DELAYED SIGN OFF GO LIVE SPRINT
DARK MODE
GO LIVE & SALES 8/30
*Teams are working on stories and plan is targeted to be finalized by 4/19 and this could change the
above timelines
WE ARE HERE
DEV DESIGN 6/14
STORY SIGN OFF 6/28
DEV INTAKE 6/28
REQUIREMENT/SCOPE 5/31
DEV COMPLETION 8/30
QA, PERF COMPLETION 9/19
UAT 10/3
PRODUCTION 10/25
Fanatics - Overall Milestone

New MVP Scope and Timelines:

● Requirement/Scope 4/19 1e
● Dev Design 4/26 sah● Story Sign Off 4/26 P● Dev In Take 4/26
● Dev Completion 6/28
● QA, Perf Completion 7/12
● UAT 8/02
● Production 8/23 (Go Live and Sales begin 8/30)

Phase 2 Scope and Timelines:

● Requirement/Scope :31-May
● Dev Design :14-Jun
● Story Sign off 28-Jun
● Dev In Take 28-Jun
● Dev Completion 30-Aug
● QA, Perf Completion 19-Sep
● UAT 3-Oct
● Production 25-Oct

*Teams are working on stories and plan is targeted to be finalized by 4/19 and this could change the
above timelines
SKU Onboarding target

MVP Launch

*Fanatics skus will be ‘online only’, not sold in the stores/available for BOPUS & BOSS.
Order Volume Projection
4/11: Tom and Direct Ship team confirmed that KT should plan for the above projections
From 250K skus
Scope for MVP (First launch - July 2019)

Item Ingestion 1. KLINK support to automate Style and SKU creation if all attribute values are provided
in advance.

2. KLINK support for automatic publish to Kohls.com without manual intervention if data provided in
advance.

3. KLINK support for mass upload images to an FTP server as part of product creation

Performance Scaling

4. Scale performance of RMS, CMS and Image upload via Censhare to support additional load

5. Scale performance of Solr

6. Scale performance of existing DSCO and all Inventory/Order Management Feeds including Sales Hub
to
downstream systems to accommodate additional SKUs and orders.

Key Assumption

No overlapping skus to be on-boarded for July MVP launch.

*Business will ensure skus that are onboarded in July will not have any overlap with current skus. Once
KT has a solve to associate multiple skus with same UPC, we will onboard the overlapping skus. Tech
solution will be needed for remaining skus to be onboarded in 2019.
Out of Scope for MVP Release

1. Mass Review & Mass Maintenance: This was not part of the original requirements/estimate.

2. Automation of CP Creation: This was not part of the original requirements/estimate.

◆Base CP creation will be automated

◆Creating customer CP is not in scope for MVP

3. New Returns Process: A new technology solution to support a new Returns process for multiple
SKUs with the same UPC.
Areas for KT effort (new dev) - MVP
- Products and sku ingestion (all attributes K-link and PMDM require) - Item, image, content setup,
Censhare - Fulfilment related attributes setup (selling channel, OCF attribution, shipping service codes,
twebitem attributes) - PMP, PDP experience, Search experience (Solr) - Inventory updates to ecomm -
Pricing & Promotions - Cart and Checkout experience (shipping methods and dates, offer/KC exclusions,
gift wrapping, pricing & promo) - Purchase history/details page - Emails - Order status & Tracking number
- Shipping price - Performics, other 3rd party apps that need the new skus - Tax - Omniture - Reporting
(Financial system updates, invoicing, marketing analytics) - Order xml - DSCO - Fanatics Integration
(non-KT) - Order Management, DSCO - OMS/GIV-OIC integration, Settlement - Returns, POS,
Warehouse applications - OCF Data Analytics - Customer Service (CSC agents) - Marketing -
Performance Scaling (to support sku growth and order volume)
*Areas not highlighted in red will only be regression testing effort from KT
Business teams will own the following activities

● Mapping of attributes for all types of products with Fanatics

○ Any business logic that is currently in place specifically for direct ship items on the site, business will
ensure that needed data is fed into the attributes by Fanatics. E.g. ‘ds’ indicator to identify Direct ship
skus. This is used in omniture reports. Other examples are TVS (pricing/offers) being aware of what sku
is of type ‘ds’ so offers exclusion rules work as expected for Fanatics items.
● Correction process if sku ingestion fails
● Ensure no overlapping UPCs are onboarded in July

● Setup data for selling channel, OCF attributes, shipping service codes/restrictions, twebitem attributes
etc
● DSCO - Fanatics integration
Risks - for MVP launch

1. DSCO-Fanatics integration discussions bringing in new scope for KT that was not planned for.

>>Need confirmation that DSCO can support all Fanatics specific requirements.

2. Fanatics does not provide a physical pack slip. So our most common return use case is not fully
supported.

>> Need Kohl’s business team to close this

3. RTV process is still under discussion between Kohl’s business and Fanatics teams.

>> Need Kohl’s business team to close this

4. Some KT teams yet to confirm estimates on what is needed to support sku growth and order volume.
Open items list
Sr. no
Question open Impact Action item Resolved:Y/N?
Resolution Needed Resolution comment:
by:
1. New Kohl’s internal sku id to be sent to
Fanatics (new process being asked). Can DSCO help pass this on to Fanatics? Otherwise it will be new
scope for KT
High Shekhar N 4/17
2. Fanatics not able to send UPC for many items
~400K skus/items. Kohl’s cannot support skus without UPC. Need confirmation from Kohl’s business that
this expectation has been setup with Fanatics
4/16
3. Fanatics unable to generate physical
packslips. How will store returns work?
High Tom Y - Fanatics and
Kohl’s business aligned that incoming skus has to have a UPC.
Medium David/Kerry N 4/17
4. RTV process that will be followed by EFC.
There is a new KT ask to pass Purchase Order ID to Fanatics
4/17
5. Systems that will need to scale to support sku
and order growth for MVP
High David/Kerry Y, no KT support in
scope as part of phase 1
High Shekhar , Prashant N 4/16
Open items list
Sr.no Question open Impact Action item Resolved:Y/N?
Resolution comment:
Resolutio n Needed by:
6 How to flip DS indicator for fanatics items
in CICS. Actually done via a cvs file load, but limited to 50,000 SKUs. Can this limit be increased?
04/16
7 How to update Taxware code for all
Fanatics items
High Katie Silcock
YColleen/Sandy/Linda
Process already allows for multiple files of up to 50,000 SKUs each to be pulled into the nightly process.
Klink/PMDM will send the list of skus to twebitem in a CSV (new story), after which Nichole and team will
kick off the process to upload ds indicator, shipping attributes etc 50k skus in each file into twebitem. K-
link will also send email to Nichole & team to let them know about new skus being created for Fanatics.
High Sandhya/Atul N 04/16
8 DS team to update data in twebitem (e.g.
shipping service code, ship alone, hazmat etc)
Medium Kerry
Y, process to be owned by & Prashant (to account for
Nichole & team. This has be this in the program timeline)
incorporated into the launch/release playbook
Open items list
Sr.no Question open Impact Action item Resolved:Y/N?
Resolution comment:
Resolutio n Needed by:
9 Who will filter the common skus with UPC already in
Kohl’s system
N. Business will filter out. During
4/17 ingestion also will error out if same UPC is already in Kohl’s (Sanjeev to confirm)
Notes/callouts from 4/10 meeting on MVP scope between business & KT

- Until the ability to same UPC to multiple vendors is not available, business will ensure no
non-Fanatics vendor skus with a Fanatics UPC are onboarded. In case a need like this arises business
will remove those skus from Fanatics and proceed. - Business to ensure correct tax codes and tax rules
are defined for the new skus - Fanatics will be made aware of Kohl’s generated sku id - Risk: Fanatics
cant do packslips. This needs to be resolved to support customer returns.Owner:
David Burns - Returns - no store associate training needed as for MVP the Kohl’s standard process of
vendor
returns to be followed. [Owner : Requesting Order ID, ETA 4/16 not in scope as mass Upload, MVP.
fanatics will accept all] - Go-live date of the items will be set to ensure all inventory and pricing data are in
the system
before items go live on the site
Appendix