Value, cost and risk scores set the migration sequence Scoring every work package for business value, cost and delivery risk sets an order that follows worth and dependency: the foundation data everything reads goes first and the high-risk legacy decommission waits, however loudly a stakeholder argues for going sooner.
Value, cost and risk scores set the migration sequence
A scored prioritisation matrix. Each row is a migration work package, with columns for business value, cost, risk and the sequence position the scores earn. A marker on every score shows whether it favours going early, argues for waiting, or points neither way: for business value a high score favours going early, and for cost and risk a low score favours going early. Foundation data, the model every other package reads, scores high value and low risk and is tinted as the lead package that goes first. Core platform goes second, the customer channel third, reporting fourth. Decommission legacy, low value and high risk, goes last. A three-state legend explains the markers.
Foundation data The model every package reads High Medium Low First Core platform Shared runtime and services High High Medium Second Customer channel The public-facing front end Medium Medium Medium Third Reporting Analytics off the new model Medium Low Low Fourth Decommission legacy Retire the systems left behind Low Low High Last Favours going early Neither way Argues for waiting
