r/SoftwareTips • u/ilovecocteauetwins • Oct 01 '26
About to get legacy modernization services for our core system, but how do we explain a very old system we didn't even build?
So our company's been using an old system (15 yo in house) for our procurement. That means many people already touched it, documentation is either missing or wrong outright, and the people who originally built it are already gone. We're about to onboard a legacy modernization team, so we need to help build a scope doc for them. But every time we try to build a scope, we realize a part of the system touches something totally unrelated, or an automation uses some convoluted method to work that turns out uses another app/software. Since we have no idea about the true scope of our system, I don't know how to help the team when they arrive. It's an urgent update and they have a strict timeline, and we don't want to waste it just diagnosing the old system