The eComm team just wrapped up a great week of User Acceptance Testing (UAT). Many thanks to an amazing team who helped make it happen:

• Virginia Berkenkotter, Alanna Steffens and Ann Early with ACF Solutions for running a successful week of testing with nearly 40 CU communicators
• Nonie Wainwright for organizing the computer lab on the Denver campus and helping with a last-minute printing project
• Elizabeth Collins and Allison O'Malley for feeding our testers
• Joanna Iturbe for her Salesforce genius and extra support
• Lisa Carr for providing her CU source system data insights
• Kyle Kirves for his project management leadership
• The entire eComm team for being engaged, present and helpful the entire week 

Here is this week's eComm project status update from Kyle Kirves, our Center of Excellence project manager. 

Ecomm Current Status:
Scope – Green;
Timeline – Yellow

Highlights:

• Test Environment built and regression tested. Code and data load complete into Test, including Exact Target/Marketing Cloud MITIGATED RISK: UAT begins 6/24. Code and data issues resolved. UAT can proceed on schedule (beginning 6/24) unless there was something that materialized today that I don’t know about.
• Functional testing by eComm personnel begins this week – on schedule. RISK: Regression 2, Functional, and UAT testing completing in parallel (typically, these would be done in order 1, 2, 3)
• Testing completed: Unit (in Test, and sign off received), Regression 1 (in Dev and Test)
• Provisioning is underway. Touch-base with campus owners this week to resolve issues and reconcile roadblocks
• Data integrations continue, with sample files exchanged by team from/for Advance. No current obstacles identified
• SuperUser/user orientation completed last week

Team continues to manage project schedule through short-term view (through UAT) to synch activities at a more granular level, focused view than top-to-bottom project plan. Regression Testing 2 in Test this week (week of 6/22), as well as Functional Testing and UAT. As mentioned last week, this does present a risk as typically UAT does not commence until after full functional and regression testing. But since this is TEST and not Prod, it is one that the project is assuming. Full data and code loads complete in advance of UAT. Developed XML code deployed to Test and errors will have to be shaken out. Timeline remains in yellow status for this week until results of UAT are in. However, if UAT completes on schedule, recommend moving to green for next week as schedule issues have been resolved for the most part. Team is much more optimistic that the timeline is attainable. As mentioned last week, provisioning planning is mostly occurring offline with meetings as necessary – concentration is now on “working” rather than “meeting” or “planning.” Some issues as to complexity and visibility into provisioning activities have surfaced this week, but believe that this is more of a communication issue than anything else. Meeting with the provisioning leads for each campus tomorrow to assess. We do need to manage expectations and make sure everyone is on the same page for scope on provisioning. Data integrations conversations continue on bi-directional data planning across systems (MDM, Advance, SFDC, etc.). Primary focus this coming week:

• Regression/functional test of Test Environment
• UAT
• Review short term schedule and revise
• Debrief with results from regression, functional, and UAT testing
• Update configuration as required
• Requirements analysis for eComm Phase 2.0

Email at contact@cu.edu with any comments or questions.