Project Management

Please login or join to subscribe to this thread

Decommission of obsolete/ legacy system examples needed

linkedin twitter facebook   Agile   Change Management   Consulting  
avatar
Ruchika Dhingra Manager| AXA XL New Delhi, Delhi, India
Share project examples in your organization to decommission legacy technology and system and move to an efficient platform
Sort By:
< 1 2 >
avatar
Valerie Welbourn Chief Operating Officer| Ed Holmes & Associates Hendersonville, Nc, United States
Jan 22, 2022 12:00 PM
Replying to Keith Novak
...
Transitioning from hand drafting to CAD systems is one many companies faced 20-30 years ago. It's not just the physical drawings involved. It also includes BOM systems, drawing storage, how drawings are used by manufacturing, etc.
Keith, that takes me back. I remember digitizers!
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
On my first project decommissioning legacy software, we were notified of the decision after the decision was made to decom it and a replacement was purchased. We started by identifying/documenting:

* who used the system
* what they used it for
* inputs into the system (manual and automated)
* outputs of the system
* integrations with other systems

Most of what we found was going to be handled by the replacement system, but there were some features that the new system couldn't handle. In some cases, additional software was built or purchased. In a couple cases, it was decided the missing features weren't important enough to replace.

I recommend understanding the legacy system and what you need it for BEFORE buying a replacement, then buying the best replacement that you can afford. Maybe we would have made the same decision if we had been allowed to do a little analysis first, but it would have been an informed decision with a better understanding of the LOE required to implement the new system and new tools for missing features.

In my last decom project, we were going to replace a legacy ERP. We spent about 6 months documenting features, functionality, and processes. This could have been done faster, but we didn't have dedicated SMEs. Data was also an important consideration - what were we going to migrate? What were we going to archive? Were we going to run the legacy system in parallel to validate financial reporting? If so, for how long?

If you're looking at decommissioning/replacing a large legacy system, look into which will be more cost effective - temporarily backfilling a few people so that you can have dedicated resources and do the work faster, or using existing resources, resulting in the work taking more time. It could go either way, but I'd lean toward having dedicated resources, if you can.
avatar
Kevin Miazek VP, Project Management| Credit Union ONE Shelby Township, MI, United States
At the credit union I work for, we are removing the traditional phone tree when you call to a chatbot/AI solution. The intent is more calls can get answered easily and quickly by asking questions instead of waiting for the "options." Plus it should reduce the number of calls that go through to an agent or the ones that do go to the agent are critical needs.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"I think popular music in this country is one of the few things in the twentieth century that have made giant strides in reverse."

- Bing Crosby

ADVERTISEMENT

Sponsors







Newsletters

Jul 8: Stop Negotiating, Start Reframing
Jun 24: Acumen Is a Process, Not a Place
Jun 17: 7 Ways to Show Business Acumen Every Day

See all newsletters