HOW TO DEVELOP DIGITAL AGILITY IN ORDER TO STRUCTURE AND ACCELERATE INTERNATIONAL BUSINESS 1
INTRODUCTION 2
HISTORY 3
4
Vision Establish the Official Canon Store as a premium retailer with unique value proposition & experiences.
Ecommerce Proposition Development CHALLENGE FOR ECOMMERCE CHANGE MANAGEMENT Create Brand competitive advantage Redefine the customers expectations Customer Centric Approach Link Ecommerce to wider business Premium customer experience Internally support new opportunities Adopt best practice Be as good as Retail Define boundaries and WOW Create Platform Build a functioning Ecom Store Internally & Externally Neutral STAGE 1 STAGE 2 STAGE 3 STAGE 4
ADAPTIBILTY IS THE NEW COMPETITIVE ADVANTAGE Via: https://hbr.org/2011/07/adaptability-the-new-competitive-advantage 7
ECOMMERCE AGILITY EASE OF NEW MARKET ENTRY: EXPEDITED ACCESS TO NEW CUSTOMERS AND NEW GEOGRAPHIES FACILE INTEGRATION OF NEW TECHNOLOGIES: QUICKLY ADOPTING INNOVATIVE SITE FEATURES AND CAPABILITIES Via: http://cdn2.hubspot.net/hubfs/197229/l2 Demandware_- _Ecommerce_Agility.pdf?t=1462974783210 DYNAMIC CONTENT CREATION: CONTINUALLY ENGAGING CUSTOMERS WITH RELEVANT AND TIMELY CONTENT 8
THE APPROACH 9
1. PEOPLE AGILITY 2. PLATFORMS 3. PROCESSES 10
PEOPLE 11
WITHOUT A GOOD TEAM YOUR FANCY AND SOPHISTICATED TOOL IS USELESS Via: http://online-behavior.com/analytics/conversion-optimization-model 12
THE RIGHT CULTURE? 13
AN INTERNATIONAL TEAM 14
COUNTRY FOCUS 15
PLATFORMS 16
STANDARDISATI ON VS. LOCALISATION 17
18
TESTING ACROSS LOCALES 20
21
PROCESSES 22
23
ECOMMERCE NEW REQUIREMENTS DEVELOPMENT PROCESS Raise a business case and come to in-tray Be prepared to clearly state your change, its impact to Canon and Ecommerce and business benefit Work with product team and sprint cadence Attend sprint planning and continually collaborate with IT and products team in JIRA during construction and hardening Show and tell and go live Attend show and tell to see what is going into the release along with your delivery and look forward to seeing your initiative go live User stories and JIRA Once requirement is accepted and prioritised, we create the EPIC and approve the user stories in JIRA and regularly monitor the ticket 04 01 02 03 Be part of testing Once requirement is ready for testing, participate in UAT working with Madhu. Sign off if you are happy. If not, identify areas to improve and retest 24
ECOMMERCE NEW REQUIREMENTS PROCESS PLAN PRE-WORK DEVELOPMENT GO-LIVE WHAT IS THE PROCESS? QUALIFICATION New requirements into Ecom channel High level assessment of new proposed functionality PRIORTISATION Backlog grooming Prioritisation against other Ecom deliverables EPIC raised in JIRA Target release date given MOBILISATION Impact analysis of the change carried out across all work streams and IT development, using the CPPOLDAT assessment DISCOVERY Requirements are refined and added to the backlog (in JIRA) in preparation for Construction User stories signed off by Product team CONSTRUCTION Sprint planning All dev and build activities 01 02 03 04 05 06 HARDENING All regression and functional testing All UAT testing and sign offs 07 GO-LIVE Overnight release activity to ensure that release has been successfully deployed with no impact to trading nor customer experience WHAT IS THE PRODUCT TEAM S ROLE? Obtain a lightweight business case from BO and have this presented at the intray meeting with clear revenue driver. Ensure that there is a go-live proposition and business roll plan Raise EPIC in JIRA Ensure that the proposed change can take high priority in the product backlog by scoring a high WSJF score. Reprioritise the backlog and roadmap in the roadmap review Own wider business readiness activities and communications Ensure all development assumptions have been met Give IT teams confidence that this is the correct thing to do CPPOLDAT completion Work with Content teams to support UI sign offs Attend discovery weekly check-in and if need be, refine the backlog and roadmap again Product Owner owns sprint backlog and user story prioritisation Chair forward look sessions Attend sprint planning Attend show and tell sessions Support cross functionally any defect fixes Sign off for requirements Product Owner and Product Manager to give go/no go Feed into post live support documentation into Confluence Attend go/no go 6am go-live call Provide successful go based on activities Support FAM with post live testing. Attend release retrospective 25
Phase Preparation Scope Locked On boarding Validation Testing Go Live Stabilization NSO Go Live BAU Handover Description - Prepare engagement materials & meeting agendas - Align playbook activ ities & - Align NSO Senior Leadership - Engage ecommerce champion - Validate R2.X component - Prov ide comms / training - On board BAU resource - Rev iew Product Data content - Conduct UAT - Conduct Customer Order - Conduct Pre Go Liv e check - Ensure CEL & NSO alignment - Prov ide hyper care support - Transition to BAU resource - Post Go Liv e Check Point timelines to project plan - Hold official NSO Kick Off Testing - Hold launch in NSO BUSINESS Objectives - Ready for NSO Kick Off - Kick Off Ecommerce in NSO - Validate inputs for release components - Deploy comms & training - Validate ecommerce site content - Ready for Go Liv e - Transition to BAU GO-LIVE PLAN Timing T-16 weeks T-15 weeks T-12 weeks T-7 weeks T-1 weeks T+0 weeks Overall % Go Live Readiness % (inc. start date) Complete Overdue In Progress 06-Jul 27-Jul Ireland 6% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 1% 0% In Progress 06-Jul 27-Jul France 6% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 1% 0% 24-Aug 31-Aug 07-Sep 12-Oct 05-Oct 27-Oct In Progress 06-Jul 27-Jul 31-Aug 12-Oct 29-Oct Germany 6% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 1% 0% In Progress 06-Jul 27-Jul 31-Aug 12-Oct 03-Nov Netherlands 6% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 1% 0% In Progress 06-Jul 03-Aug 14-Sep 02-Nov 30-Nov Italy 6% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 1% 0% 26
BAU WEEKLY TRACKERS 27
SUMMARY Conversion Rate Optimisation 28
Digital Culture International Outlook RECIPE FOR SUCCESS Personalisation Conversion Flexible Platforms Planning Tools Agile Team 29
ALWAYS TESTING ALWAYS LEARNING DIGITAL AGILITY ISN T JUST TECHNOLOGY, IT S A MINDSET ALWAYS GROWING ALWAYS CONVERTING 30