Hi Keith,
planning in my environment consists of several layers:
1. technical updates on the devices (consoles, tablet pc´s, sometimes smartphones)
2. estimating training needs for new features, bug fixes …
3. testing (unit test and integration test)
Planning for 1. requires scheduling the update so that in ALL locations all devices run the
same/compatible firmware. One major objective is, being able to “backup” one location with e.g. a console
from another in case of problems (we never had so far!!!).
Planning for 2. answers the question, whether the update requires training for the users (FOH, musicians, etc.)
Sometimes the release notes are Ok for that purpose in some cases not (e.g. ganging).
Planning for 3. in the first line is, testing the update on one device. The integration test is more complex,
because all associated functions must be tested: recording, hearing aid systems, video sound, etc.
All this must be scheduled, communicated and put in execution.
To your dedicated questions:
1. Yes, we have visit the consoles.
2. Two Admins, but always one is selected to run an update.
3. No, I foresee the update and ensure all devices are touched.
The lead time for the 1.4 update was ~6 weeks.
Did this enlighten the comment on planning?
:-)) sunny week
Thomas.
