Now, several years after starting this project, all programming is complete and ready for production on our development end. On other side, the client is still revamping screens and changing structures, without having conducted any user testing at all. The reason? The client is "waiting until development is finished."
Each week's project conference call produces new changes in every part of the contact, policy, claim, and reporting subsystems. Also, as per the agreement worked out at the beginning, we've tried to conduct training sessions for the new product. But the client claimed it "knew it all" and stopped this process.
On the bright side, this situation is the source of much humor during our company's status meetings, and the client continues to pay for the additional programming and support costs that keep piling up. Even though we are tired of working on the project, it may be a continuous source of income for many years to come.
Get a $50 American Express gift cheque if we publish your tech experiences. Send your story of a lesson learned, of dealing with frustrating coworkers or end-users, or a story that illustrates a relevant takeaway to today's IT profession to email@example.com.
This story, "We don't need no stinking IT specs!," was originally published at InfoWorld.com. Read more crazy-but-true stories in the anonymous Off the Record blog at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.