7.1 Release Charter v3 02.17.12 New

8/3/2019 7.1 Release Charter v3 02.17.12 New

1/17

RELEASE: 7.1 MAY 16TH

, 2012VERSION: 0.1 DATE: 02/13/2012

This document is confidential and proprietary information of The Home Depot. Page i

THE HOME DEPOT

7.1 RELEASE CHARTER

Release Go Live Date: 05/16/2012

Version Number 0.1

Draft/Final as of 1/12 /2012

Printed on 2/20/2012

Document

Owner(s)

Kaushal Patel

Annie Barua


2/17

RELEASE: 7.1 MAY 16

TH, 2012

Version: 0.1 Date: 02/13/2012

This document is confidential and proprietary information of The Home Depot. Page i

Document Information

Document Purpose

The purpose of this document is to confirm scope and schedule for online technology

PIP/PLP/Check out redesign Release 7.1 (Go Live: May 16 2012). The document serves to

enable us as a team to make sure that all resources (Quality Analyst, Project Management,

Business Analyst, Development and Management) have a shared understanding of the release

contents, priorities, constraints, timelines, environments, resources and document repositories. If

or when additional projects are added to the release after the commencement of QA activities,

this document will help to serve as a baseline for determining impact to current milestones or

timelines.

This document and any related project documents are accessible via the PIP/PLP/Check Out

Redesign Release 7.1 on SharePoint site at the end of this document. For any questions

regarding this project, please contact Kaushal Patel; Ext# 85576.

Email:[email protected].

Revision History

Version Date Summary of ChangesRevision

Marks

0.1 1/12/2012 Initial Draft

0.2 1/30/2012 Updated Project information and Timelines

0.3 Included additional scope

1.0 Added approvals


3/17

RELEASE: 7.1 MAY 16

TH, 2012

Version: 0.1 Date: 02/13/2012

This document is confidential and proprietary information of The Home Depot. Page ii

Approvals:

The following have approved this document.

Name Title & Department Approval Date Signature

Juanita Smith Online Technology QA Mgr.

Annie Barua Release Management Lead

John Anthony Performance Lead

Christopher Grant Architect

Dahesh Patel Sr. Architect

Bonnie Jones Project Mgr. (PIP)

Romona Denial Project Mgr. (PLP)

Tia Likely Sr. IT Mgr. FED (PIP/PLP)

Tiffany HaymanSolutions Delivery Manager

(PIP/PLP)

Venkateswarlu Pabbuleti QA Lead (PIP)

Surabhi Chowdhary QA Lead (PLP)

Ravi Nudurumati Dev. Mgr. (PIP/PLP)

Mike Marcella QA/QP Manager (PIP/PLP)

Tadi Prabhakar QA Lead(PLP)

Barrios Guillermo UAT Manager

Devangi GandhiProject Manager (Check out

redesign)

David Albracht Business Lead Manager

Craig Sultan Business Sponsor - Sr. Mgr.,Major Business Initiatives

Cara KinzeyIT VP Sr. Vice President,

Information Technology

Matt JonesGeneral Mgr., MobileHomedepot.com

Tom SweeneySr Director, ProgramManagement

Lyn MuellerDirector, ProductManagement


4/17

RELEASE: 7.1 MAY 16

TH, 2012

Version: 0.1 Date: 02/13/2012

This document is confidential and proprietary information of The Home Depot. Page iii

Additional Distribution:

Track Lead

Catalog & Navigation Venkat KatpalliSearch & Page Builder Eugene Liang

Checkout & Promotions Doug Robinson

DB Migration Dan Perritte

CMC, Account & Multi

Variant Vijay Jeevaraj

Integrations Meyyappan

Infrastructure Devangi / Scott


5/17

RELEASE: 7.1 MAY 16

TH, 2012

Version: 0.1 Date: 02/13/2012

This document is confidential and proprietary information of The Home Depot. Page iv

Table of Contents:

1. RELEASE SCOPE...06

1.1. IN SCOPE..06

1.2. OUT OF SCOPE .. 07

1.3. RELEASE COMMUNICATION PLAN ................................................................................. 09

2. RELEASE TEST STRATEGY...09

2.1.INCLUSIONS..09

2.2. EXCLUSIONS................................................................................................................. 09

2.3. LINK TO WEEKLY RELEASE DASHBOARD..09

2.4. TOUCH POINTS FROM REGRESSION.10

3. RELEASE RESOURCES10

3.1. RELEASE RESOURCES.................................................................................................... 10

3.2. PROJECT RESOURCES ................................................ERROR!BOOKMARK NOT DEFINED.

4. ROLL BACK PLAN11

4.1. ROLL BACKPLAN...................................................................................................... 13

4.2. ROLLBACKDECISION PROCEDURE ............................................................................. 13

5. ENVIRONMENT AVAILABILITY..14

5.1. IMPLEMENTATION AND VALIDATION PLANS ................................................................... 14

6. RELEASE DETAILS...15

7. RELEASE ENTRANCE CRITERIA16

7.1 GENERAL ENTRANCE CRITERIA:...16

8. FINAL RELEASE CANDIDATE CRITERIA

..166

THE FINAL RELEASE CANDIDATE WILL BE BUILT FOLLOWING COMPLETION OF

FINAL UAT, PERFORMANCE, FUNCTIONAL AND REGRESSION TESTING. THIS WILL


6/17

RELEASE: 7.1 MAY 16

TH, 2012

Version: 0.1 Date: 02/13/2012

This document is confidential and proprietary information of The Home Depot. Page v

BE USED FOR BACK-OUT AND RE-IMPLEMENTATION VALIDATION.

.166

9. SHAREPOINT SITE

...166

10. LINK TO SUPPORT TRANSITION DOCUMENT, PRODUCTION SUPPORT

DOCUMENT.

..166

11. CODE BRANCH DETAILS

...166

DEVELOPERS TO INCLUDE NOTES EXCHANGED DURING BUILD IN THIS

FOLDER

..166

Critical Success Factors

Introduction:

This section describes Critical Success factors (CSFs) for the ReleaseManagement process.

Success Factors:

The Critical Success Factors (CSFs) are:

y Producing Operable Solutions

y Controlling Releases into Production

y Implementing Releases into Production on Time

Deployment Notes (ECRs):

Release Notes :


7/17

RELEASE: 7.1 MAY 16TH, 2012

Version: 0.1 Date: 02/13/2012

This document is confidential and proprietary information of The Home Depot. Page 6

1 Release Scope

Projects approved as part ofPIP/PLP/Check out redesign for Release 7.1 here:

1.1.1 In Scope: PIP

1. Page Functionality Enhancements - new functionality and UI enhancements to itemson a PIP itself.

2. Analytics - New metrics that will be tracked on a PIP.3. Defect Fixes - Fixes of defects previously documented within QC and directly

affecting a PIP.

1.1.2 In Scope: PLP

1. Product and Content Relevancy.

2. Online Monetization.3. Product Recommendations.4. Performance

y Improve page performance (Per IT the assumption is that upgrade to WCS7 wouldprovide performance improvements) (required performance metrics documented inSLA document)

5. Defects -Fixing selected high priority defects

1.1.3 In Scope: Check out redesign

1 SSL Certificate LogoSwitch SSL certificate provider from COMODO to VeriSign. Users should see the

VeriSign trust mark in the global footer, in the cart, and in the Checkout pages tobolster their confidence in purchasing online at homedepot.com.

2 Checkout Sign-In Page Redesign

The primary call to action should be existing user sign-in rather than guest

checkout to promote ease of checkout and higher conversion rates.

3 Tax Exempt PurchasesCustomers who (1) have an existing Home Depot tax exempt ID or (2) utilize

government credit cards with certain BIN numbers should be able to have no taxapplied to their order.

4 Commercial Credit Card Purchase Order EnhancementUsers of commercial credit cards (issued by THD or commercial banks) should have

the ability to enter PO numbers for exact replication on the users credit card statementto facilitate invoicing of purchased items.


8/17


Version: 0.1 Date: 02/13/2012


1.2 Out of Scope:

1.2.1 Out of Scope: PIP

The following table identifies out of scope items for this initiative.

# Out of Scope Comments

1. Performance EnhancementsPerformance enhancements previously recommended by IThave been de-scoped for this project phase due to the updates

made during WCS7.

2. Defect 12578- Searching on Product in Google does notdisplay the right PIP.

3. Changes to display all price points have been deferred.The System will display all applicable price points on all PIPs.

For example,

- List Price- Was Price (promotional price)

- Price (current price)

4. DEFECTS_10285 - Search results back from PIP does notretain sort.

5. Hide IRG PODsIf Collections, Accessories, and Coordinating items have fewer

than three (3) products, then that section should be hidden from

the PIP, and the page should hide the white space where thatIRG POD was displayed, and all content below the IRG, will beshifted upwards on the page

6. Display Order of PIP ContentAbility to display Robust Product Content above and below

IRG Display (e.g. Product Description and Shipping Info aboveIRG and Specs, Reviews, More Info below IRG content).

7. Certona Recommendations Display LocationMove Certona Recommendations from Right Rail and move to

a horizontal display below IRG PODs. Expand width of displayof product content below product imagery (i.e. IRG, Robust

Product Content) to accommodate removal of CertonaRecommendations from Right Rail. If there is no Certona

content, shift up other product content.

8. Expose Reviews for organic search on PIPsThe System will allow Reviews (located in the SuppportContent section) to be searched by external search engines.


9/17


Version: 0.1 Date: 02/13/2012


1.2.2 Out of Scope: PLP

The following table identifies out of scope items for this initiative.

# Out of Scope Item Comments

1. Performance enhancements previously recommended by IThave been de-scoped for this project phase due to the

updates made during WCS7.

2. Manual ordering of left navigation refinement filters.

3. Any functionality requiring changes to Certona API.4. SKU Level promotion messaging.

5. DEFECTS_10193 - R4.6 IRG Enhancement: Many of theProducts are displaying Product Description in Two linesand Ellipses in 3rd line

6. Removing duplicates in Breadcrumb.

7. Changes to display all price points have been deferred.

The System will display all applicable price points on allPLPs.

For example,

List PriceWas Price (promotional price)

- Price (current price)

8. Updating Google Ads is not part of Release 1.

1.2.3 Out of Scope: Check out redesign

The following list of features have been defined as out of scope for the Checkout Redesign

Release 1 project

1 Mobile Application Development

While customers will have the ability to checkout using a mobile or tablet device,

there will not be mobile application development within the scope of this project.

2 CTC Development

While customers can place orders by calling Customer Service, there will not be CTCdevelopment to allow for the entry of a commercial PO number.


10/17


Version: 0.1 Date: 02/13/2012


1.3 Release Communication Plan:

Audience Content Vehicle Target

Date

Owner Status

Name and

role of person

who will be

communicate

d

Purpose for

communicatin

g (i.e. project

status update,

financial

status update,

review issue

Method of

communicating(i.

e. email, meeting,

report)

When

the

message

is to be

delivere

d by

Person

responsible

for ensuring

that the

message is

received

When the

communicatio

n is completed

Onlinetechnology

leadership

Project status Email Weekly Bonnie /Romona

/Devangi

Project PMs,

RCs

Environment

Readiness

updates

Email Daily Bartholome

w Burkhard

/ Annie

Barua

2 Release Test Strategy:

2.1 Attached Spreadsheet:

QA Approach for PLP

Redesign.docx

2.3 Dash Board Link:

https://portal.homedepot.com/sites/OnlineITPlan/PM/RlsMgmt/Release%20Documents/Forms/AllItems.aspx?RootFolder=%2Fsites%2FOnli

neITPlan%2FPM%2FRlsMgmt%2FRelease%20Documents%2FRelease%207%2E1%20%28%20features%20release%29&FolderCTID=0x


11/17


Version: 0.1 Date: 02/13/2012


01200043F3E3C214A9C54B9C33B09BF60C036A&View={9B697AE4-0C3E-4D8C-8897-

34D45C8F13C4}&InitialTabId=Ribbon%2EDocument&VisibilityContext=WSSTabPersistence

2.4Touch points from Regression:

3 Release Resources

3.1Release Resources

y Release Coordinator/Manager : Kaushal Patel/Annie Barua

y Build Engineer: /James

3.2Project Resource:

Developer

Manager

Project

Manager

Development

LeadArchitect

QA Lead

QA

manager

PIP

Tiffany

Hayman/Rav

i Nudurumati

Bonnie

Jones

Iyengar

Geethanjali

Christopher

Grant

Pabbuleti,

Venkatesw

arlu

Mike

Marcella

PLP

Tiffany

Hayman/Ndu

rumati Ravi

Romona

Daniels

Barnett

Damond R

Christopher

Grant

Surabhi

/Tadi P

Mike

Marcella

CCRM

Barthlolome

w Burkhard

Raghu

Emmadi

Enhancem

ent/Defects

Muzzamil

Akram

Vijay

Eamani

Kavitha

Veeturi

Check out

redesign

Devangi

Gandhi

Dahesh

Patel

4. Build details

4.1. Impact analysis by defect

4.1.1. Impact to Mobile platform, George Augustine.

4.1.2. Impact to .com


12/17


Version: 0.1 Date: 02/13/2012


4.1.3. Impact to Vendor management system

4.1.4. FED Impact analysis Brandon Moore

Version Date Summary of Changes

Revision

Marks

1.0

1.1

1.2

1.3

1.4

Release Timelines (High Level)

High level timelines below show dates by which each participating project will have to adhere

to in order for the release to be successfully released on the scheduled Go-Live date.

7.1 schedule

Date

Due

Task/Event Days

to

go

live

Activity Delivery

date

Comments

1/31 Event 106 7.1 1/31

2/29 Event Scope Freeze Date after which no

additional functionality will

be included in the release.

1/27-

3/23

Task 110-

61

Development

3/29 Event Functional

Code Freeze

This is the date by which

individual project

functionality and known Sev

3, 4 and 5 defects should be

finalized and delivered to


13/17


Version: 0.1 Date: 02/13/2012


QA. (No new functionality

added to code base).

Task Integrated

testing/

Unit testing

3/16-

4/13

Task 60-

27

QA 4/13

4/13 Event Soft Code

Freeze

4/13 Date by which all project

and development

enhancements that are to be

delivered to QA in

preparation for testing.

4/16-

4/27

Task 30-

26

UAT 4/20

4/30 Event 16 Final Code

Update

Date on which latest

production code (or code

about to go to production) is

merged with the release

code. All efforts should be

made to ensure that this date

happens before

UAT/Regression testing.

Signals end of UAT and

Business Sign off.

4/13-

5/3

Task 33-

13

QP 4/20

4/27 Event 19 Hard code

freeze

4/27

Event Build

candidate


14/17


Version: 0.1 Date: 02/13/2012


identified

Event Pre-prod Back out/final

implementation testing can

begin. No additional changes

to code.

5/15 Task 1 Go no go 5/15

5/16 Event 0 GO LIVE 5/16 Pending

5/30 Task -15 Warranty

period

4 Roll back Plan

4.1Roll Back Plan:

4.2Rollback Decision Procedure:

Description Details Who When

1


15/17


Version: 0.1 Date: 02/13/2012


5 Environment Availability

Environment availability shows what QA environments have been reserved for projects in the

release and when they will be available for use.

Environment URLs Available Dates

AD72-Development 1/17/2012

QA72 2/28/2012

QP71- cell 1 3/17/2012

QP 71 Cell 2

OMS etc

POS Stores

Documentum + any other

envs used

Pagebuilder

5.1Implementation and validation plans


16/17

15


6 Release details

6.1Release Entrance Criteria:

After this charter has been signed off, the information below will be required in order to

accept a project or break fix into the release.

6.2General Entrance Criteria:

This is the information that is required from all projects or break fixes prior to acceptance into

the release:

y Billing Information (Where will the project or break fix be billed to).

y

Completed LOEs from QA and Dev.y QA and Dev resources identified

6.3Required Signoffs per Milestone:

This highlights the impact and signoff required based on what milestones have been reached

by the project:

6.3.1 Functional Code Freeze

Variance Risk Level 1: After this date, any unplanned enhancements require approval of the

following roles:

y Impacted Project Manager(s)

y Impacted Development Manager(s)

y QA Manager.

6.3.2 Soft Code Freeze

Variance Risk Level 2: After this date, any new functionality or fixes require the approval

of the following roles:

y All release Project Managers

y All release Development Managers

y QA Manager(s)

y Impacted Product Owner(s)


17/17

16


Targeted regression testing will be scheduled during UAT to accommodate any

fixes/additional code. There is a risk that timelines may not allow for full regression and/or

cross browser testing.

In addition, non functional testing such as kiosk, web terms, etc. may occur after this date.

All deferred defects must be reviewed and agreed up by Web Operations and Product

Management minimum of 3 business days prior to end of UAT.

6.3.3 Hard Code Freeze

Variance Risk Level 3: After this date, any code changes require the approval of all the

following:

y All release Project Managers

y All release Development Manager

y QA Manager(s)

y Web Operations Manager

y Lyn Mueller

y Naveen Krishna

6.4Final Release Candidate Criteria

The final release candidate will be built following completion of final UAT, Performance,

Functional and Regression Testing. This will be used for back-out and re-implementation

validation.

7 SharePoint Site:

The SharePoint will be contain this document, any other related release documents and a

continually update on the current release status.

7.1.0 Release share point link:

https://portal.homedepot.com/sites/PMO_PLP_Redesign/Project%20Documents/Forms/AllItems.aspx

https://portal.homedepot.com/sites/OnlineITPlan/PM/RlsMgmt/Release%20Documents/Forms/AllItems.aspx?RootFolder=%2Fsites%2FOnli

neITPlan%2FPM%2FRlsMgmt%2FRelease%20Documents%2FRelease%207%2E1%20%28%20features%20release%29&FolderCTID=0x

01200043F3E3C214A9C54B9C33B09BF60C036A&View={9B697AE4-0C3E-4D8C-8897-

34D45C8F13C4}&InitialTabId=Ribbon%2EDocument&VisibilityContext=WSSTabPersistence

8.1 Link to support transition document, production support document.

8.2 Code branch details

Developers to include notes exchanged during build in this folder

7.1 Release Charter v3 02.17.12 New

Documents

Transcript of 7.1 Release Charter v3 02.17.12 New