Gord_in_Toronto
Penultimate Amazing
- Joined
- Jul 22, 2006
- Messages
- 26,494
But whoever writes the test plan should at least talk to the users, when coming up with workflows to test. My last implemenation project had a horrific testing because the idiots writing the test plans knew nothing about the workflow, and would order the testers (who were the builders anyway, but by making us follow undeviatingly from their mighty test plan supposedly that was cancelled out) to do the test plans exactly as written no matter how nonsensical or impossible they were.
My favorite was a week-long argument trying to get them to understand that even the best clinics aren't doing liver transplants as outpatient procedures, and that's why it's impossible to schedule one that way in our system. They insisted it was shoddy build rather than legitimate medical practice that made that not work. They also didn't understand why we made it impossible to schedule dead people for future follow-up appointments. No offense, public, but after you die your doctors don't care whether your weight is in an acceptable BMI range. After death you are allowed to let yourself go. Most people lose weight postmortem, gradually if buried and a lot at once if cremated.
"Talk to the USERS"? Whoever in Hell does that at any stage of a project? My wife in her working career as a user lived through three complete rewrites of the system her department used. Each one was more user unfriendly than the previous. At the time number three was launched productivity became so bad that management rolled thing back to the previous version (and, considering what that must have cost in human resources, this illustrates how bad it was) and started over. This time she said, "We had some guys come and talk to us and to see what we do; that's never happened before!"

Last edited: