Check for bug fixes, features (~~new bugs~~), or enhancements
Get the internal subject-matter experts to review tests and assemble a team to do the testing.
Thow away any spreadsheet tracking you have and use a Test Management System (see Must Haves below).
Schedule (in house or with your vendor) a fresh copy of Production to Test.
- Having a second copy of your catalog pointed at your test environment is highly recommended.
As staff test, the IT Department tests workflow tools, scripts, or SIP services.
As issues are discovered during testing, other staff validate and document findings.
After testing, review with all team leads failures or new workarounds.
Update documentation and standard operating procedures, then communicate the changes to staff.

Must Haves!

Proper Prior Planning Prevents Poor Performance
- Check for bug fixes, features (~~new bugs~~), or enhancements
- Schedule time with your staff.
Organizational buy-in and dedicated staff time
End user investigation by just “doing the regular job” in both systems.
NO SPREADSHEETS (never, ever again)
- Use a Test Management Software – QaraTMS or Quack (we liked them both).
Review all findings and give everyone’s concerns equal weight when considering the go/no-go before upgrade.
Benefits of organized processes
- No ~~(fewer)~~ surprises. Nope. None, never a surprise.
- Repetition brings smoother upgrades
~~Complaints~~ Feedback management
- Ask testing staff how testing went before upgrading production and gather feedback for improvement next time.
- Having staff volunteer to help test mitigates resentment if things weren’t “tested enough” before upgrades and offers a way to learn more about FOLIO and how JIRA works.

Stanford

TAMU

...