by Dwayne Phillips
Sometimes we have to update the technology even when old technology still does the job.
Requirements are real. We work to meet requirements in systems. Once the requirements are met, that is it. But what about the people?
Many years ago, I worked with a system that used old technology. It was embarrassing how old it was. Several people proclaimed, “Come on! We have to replace that with current technology!”
A senior manager replied, “The old technology meets the requirements. Current technology will require a new design, implementation, test, integration, test, etc., and that means money, money, and more money.”
Several years later, I had the same experience. We used technology so old that it was embarrassing. People wanted to replace it, but it met requirements. A young engineering hit me with, “But it’s 20xx. If we are stuck with this technology, I’m gone.”
There are times that the morale and pride of the people who work with systems become paramount. Old technology can truly be embarrassing, and there is a point when people won’t work with it. They will leave.
This is another example of including persons in the definition of a system. No persons, no system. Project managers and others must accept that.
0 responses so far ↓
There are no comments yet...Kick things off by filling out the form below.
Leave a Comment