20230712 - Unity Rollout Status Report
Current progress of Unity testing, development, and deployment.
RISKS
Migration time
Establish upgrade procedures and version controls for live clients on a single code version.
Need agreement by all internal teams so that client communication is aligned.
Needs to be clearly communicate to clients so they understand the future process.
Need to confirm any risk associated with testing on one type of environment and going live on another.
Need standard timeline of deploying latest branch, there is a calendar that a few have seen internally and gme/terra have seen
For Unity-Upstream2
We will need to have db loaded for each one to test regulatory in all the different states(8 total, possibly can exclude 2)
Bank formats
Land/Contract Management needs heavy regression (170/290 features were WPX)
For Unity-Midstream1
Bank formats
Fixed assets
Resource constraints internally
Chris Peterson(M33) assisting in who and how to target on initial call. Continued discussion scheduled 7/10
Services to begin assisting Midstream regression testing to meet Aug1 deadline
Micah, Blake, Ryan putting together Midstream specific test cases
GAPS
Release Notes (Jeff Gunter/Michael Ferrante actively working on)
Need process put in place to combine deltas as new clients onboard to Unity
Active projects versioning and communication
Internal project box alignment
Rewrite SOC documentation for delivering patches, releases etc
Internal Feedback/Questions
Vital experiencing positive UAT of Unity
Quote from their DO users: “we dread going back into Prod because Unity is so much better”
We create new Prod environments for cutover. Do we do this as well for their non-Prod? If not, what’s the risk?
Current Status
TERRA (Live 5/22) Yellow
Issues since go-live (46)
Closed-31, Code Change in progress-1, Support Review-11, Waiting for feedback-0, Waiting on CloudOps-3
GME (Live 5/22) Red
Issues since go-live (47)
Closed-26, Code Change in progress-2, Support Review-16, Waiting for feedback-2, Waiting on CloudOps-1
IKAV (Live 6/12) Green
Issues since go-live (51)
Closed-26, Code Change in progress-3, Support Review-14, Waiting for feedback-5, Waiting on CloudOps-0, Canceled-3
Flywheel (UAT- GOING LIVE 7/14) Green
0 open tickets
1 UAT down due to bad refresh
Vital (UAT) Yellow
7 open tickets(4 code change, 2 support review, 1 waiting on DevOps)
potentially move to upstream phase 2, discussing go-live timeline next week
Riverbend (UAT-GOING LIVE 7/21) Green
2 open tickets (both in support review)
Highpeak (UAT) Yellow
0 open tickets
Internal regression testing(QA)
Upstream
Phase 2 has not started. Jaybee will likely be test database
Midstream
Eagleclaw
96% complete (High risk)
15% complete remaining test cases(492 untested)
Transportation
N/A
Live clients' logged ticket count in backlog: 71
Dev queue: 11
Support queue: 47
Waiting on DevOps: 4
Waiting for Feedback (from client):9
Future Process Improvements
Build RACI matrix for future efforts for transparency of responsibilities across teams.
Add automation for the “easy” wins like UI testing to eliminate almost 30% of the testing effort.
Continue to build out test cases for regression testing across the application.
Add expected results to compare against for testers with limited functional knowledge.
Have defined performance testing with PROD comparable environments to provide better expectations to clients when taking code.
Add code test coverage to eliminate lost functionality with future merges or code changes.
During current round of testing multiple issues have re-emerged after originally fixed.
Important Links | Regression testing dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10080 Release 10.2.0 Dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10077 |
Clients in upgrade pipeline | Jaybee, AEC |

