• Created by Unknown User (leslie.obourn), last modified on Sep 15, 2021
  1. Each page will use the 'Integration' type ticket.  Statuses:
    1. Design
    2. Design Review
    3. Build - The developer builds and unit tests the prototype and moves to Unit Test when ready for UVA testing.  Build % Complete:
      1. 60% - Prototype is ready for unit testing
      2. 80% - UVA or Accenture Team making development updates (as assigned)
      3. 100% - Build Complete and Ready for E2E Testing
    4. Unit Test - The UVA team tests and enters tickets for requested updates
      1. Tickets where the prototype is not working as designed are assigned to ACN developer.
      2. Tickets where a prototype update is requested are assigned to a UVA developer. 
      3. The developer unit tests and moves it to End to End Test once it is ready for team testing
      4. Unit Test %
        1. 20% - UVA team is testing
        2. 40% and 60% - UVA Team has feedback
        3. 80% - Final testing (all known issues resolved)
        4. 100% - Testing complete, issues resolved, Ready for E2E.
    5. End to End Test
      1. Fail
      2. Resolve
      3. Retest
    6. Build Review
      1. Let's use this status to transition the Prototype tickets to the UVA Developers
    7. Done
    8. Note: Items required to complete the prototype will be Action Items with a label of UVA_Prod_Enhancement. The INT tickets 
  2. Each Enhancement Request will be an Action Item
    1. Label - UVA_Prod_Enhancement
  3.  Labels:
    1. UVA_SIS_Prototype
  4. Tracking Status:
    1. Design Completion: 
    2. Build Completion:
    3. Testing Completion:




  • No labels