We are embarking on a long-term project to get up-to-date with our Baan service packs on our installation of Baan 5.0c. We expect this to take well over a year.

As part of the process, I have forewarned a half-dozen of our departments that they need to provide a skilled person to test each service pack and that this person will need to supply (on average) two full workings days a month for testing for each service pack.

The user-management community does not believe this is realistic (mostly for their own perceived shortage of resources). I am asking for feedback from others who have done or routinely do service pack upgrades as to how much user involvement you get in the testing of each service pack before it goes into production.

The user-management community does not believe this is realistic (mostly for their own perceived shortage of resources). I am asking for feedback from others who have done or routinely do service pack upgrades as to how much user involvement you get in the testing of each service pack before it goes into production.

Keep pushing for this - we did similar process (month not year!) and did get active participation. We could/should have allocated a bit more time for the testing, but what time we spent was WELL worth while.

The More the Better

Unless there is a downtime constraint keeping you from installing all the SPs at once, i would install them all (in test) and have the users spend a month or so
testing the finished product. Having them spend time testing a system that will be fairly dynamic won't be perceived by them as a good use of their time and you're less likely to get buy in.

Dave

In hindsight, we tested too much of the obvious (yes, we could still set up items & create sales orders etc) The bit we got caught out on was the 'happens occaisionally' situation where we overlooked these - low usage must mean low importance - WRONG