Proposed Process Flow (Draft)

Ticket for Scoping
Brands to provide new tickets for the Sprint.

Tickets
applicable to
both US
and CA

Capacity calculation
All tickets to be reviewed, and queries/question will be raised. Ensure tickets are ready for scoping.

Estimation (Scoping)
Impact assessment & estimation for tickets. Tickets are added to the sprint when capacity is available.

Prioritize & Approve tickets.
Brand approves the tickets for monthly release or remove tickets

Capacity Review
Prepare an updated capacity plan for the sprint. Review with brands and prioritize if tickets are over-capacity.

Sprint Execution
Develop and release tickets for QA. Review ticket progress and raise issues /dependencies for resolution and next steps.

Tickets Due
Tickets are released for QA as per due date. Any fixes as part of QA/UAT.

QA Sign-off.
CA Merch team to complete testing and assign for UAT

UAT Sign-off.
CORE Brand team to complete UAT and provide sign-off for PROD release

Live Replication
Co-ordinate and replicate tickets to production.

Tickets validation on PROD.
Validate tickets in PROD.

Post implementation review
Review to check for site metrics, issues and KPI analysis. Tickets coming out of these activities are added to backlog.