SPRINT A - Define the Batch

  1. Select conversion candidate for the batch and define scope
    1. Target a good number of pages with the same component composition
  2. Query Sitecore within scope for code components & plan needed conversions
    2. UI will create and update the Mapping of Converted Components
  3. Query Sitecore Content Areas (RichText & CustomScripts) within scope forEditorial Generated UI& start planning for remediation
    1. UI will audit and update the Remediation Steps for Sprint C
  4. Groom 
    1. Provide a list of the components to UI for conversion. 
    2. Provide a list of templates that need to be constructed.
    3. UI will earmark any Jira Tickets for component conversion ARCHES Component Conversion
    4. UI will earmark any needed New Components from the Audit of Editorial Generated UI Creating A New ACC.org Component
  5. Calculate and Plan Next Sprints
    1. How complex will the conversions be/How long will it take? Generally, this will hopefully be doable in one sprint assuming there is not any major rebuilding needed. Most importantly we need to determine how many will need to be rebuilt completely. 

#acc/arches/conversion #acc/guidance