...
Negotiate scheduled upgrade with our hosting vendor. We make sure that the upgrade schedule happens when a majority of our committee members are availableavoids major campus events and maximizes staff availability.
We always use the same dry run environment that is a snapshot of our production
Rename our Slack Channel from last flower to current release. When we get back to Massachusetts, this will be from #poppy-upgrade to #quesnelia-upgrade
Our FOLIO Systems Coordinator ensures environment is ready (upgrade scripts are run, permissions are set, etc.)
Prepare spreadsheet to log issues. This is where we track if the issue is fixable, blocked, or just beware of unforeseen functionality or issues
Can be fixed by hosting prior to upgrade
Staff should be aware or will require a workaround
blocks the upgrade
Committees review their UAT forms to make sure it covers new functionality
Committees also request if new functionality needs additional time to be reviewed before being rolled out to staff (Lists App Beta)
We have 1 week for all committees to do UAT
Each committee have their own process. The focus is End to End tasks and workflows that involve multiple FOLIO Apps or cross app interaction
Issues are tracked in our spreadsheet. Issues are determined to be fixable, blocking or “beware”. Issues with beware are often surprising functionality that we didn’t see or experience before (Call Number Browse). For some issues, we report this to our hosting vendor.We report all issues that are not documented to hosting provider
Some committees work together in a meeting to do parts of the UAT. Others work asynchronously
At the end of the week, the chairs of the committees approve or don’t approve of the upgrade. And yes, there was a time when we didn’t approve an upgrade. We want “Can we live with it” rather than “Is everything perfect”
...