Details

We need to devise a pilot plan for the updated M2 site. This plan should include how to roll out M2 and how for roll back in the event an issue arises. The goal is to write testable stories for each aspect of the roll out and roll back.

We want to be able to roll the framework out to a select subset of pilot locations. Once a site has been switch to M2 we need to be able to enable or disable M2 pages by menu header. We need to be able to quickly revert the entire pilot group or a specific site back to legacy Mobile should a problem arise.

Roll Out

1. Enable M2 framework per store.
   1. We need to be able to enable the M2 header, menu, user options, settings, and workflow.
   2. All undeveloped, untested, or unreleased pages should be presented to the user via iframe
2. As whole sections of M2 are completed we need to be able to roll out functionality by top-level menu group.
   1. We will not enable M2 functionality by specific page.

Roll Back

1. We need the ability to immediately roll back a whole site or all the sites to legacy Mobile if an issue arises.
2. We need the ability to roll back a menu group of a single site or a menu group of all sites by to legacy Mobile (iframe) without having to roll back the whole site/s.

Completed Pilot and GA Release

1. Once the whole M2 project is done and we have released all the pages to the general population, and special configurations, groups, or permissions specific to the pilot should be removed so that we do not have to manage those going forward.

Mobile2 Configurations Hierarchy

• Mobile
  • Mobile2
    • Enable SSO to M2
    • Enable M2 "Forecasting"
    • Enable M2 "Input Inv. Counts"
    • Enable M2 "Create/Receive Order"
    • Enable M2 "Inventory Transfer"
    • Enable M2 "Inv. & Order Setup"
    • Enable M2 "Cash Management"
    • Enable M2 "Production"
    • Enable M2 "Inventory Adjustments"
    • Enable M2 "Customers"
    • Enable M2 "Reports"
    • Enable M2 "Utilities"
    • Enable M2 "Administration"
    • Enable M2 "End of Month"