A review before a rewrite or migration
An example scope for a read-only system review: clarify the decision, examine an agreed system, compare options, and leave a short decision memo.
- Understand the current system
- Compare credible options
- Write the next decision
The decision to make
A system may be expensive to run, fragile to change, or difficult for its owner to understand. A rewrite or migration can sound like the obvious answer before anyone has compared it with repairing the existing system.
The review starts with the decision: what needs to change, what must keep working, and what evidence would justify committing to the next step?
A bounded review
One application or hosting stack, examined read-only over one working week from the agreed kickoff and necessary access. The scope, acceptance criteria, fee, and schedule are agreed before work starts; this is a proposed timebox, not current availability.
We agree on one system, the questions to answer, and the information that can be examined. The assessment is read-only. It can use authorized documentation, a walkthrough, and access to the agreed environment.
The scope should identify the system’s role in the business, its dependencies, who operates it, and the parts that create risk or cost. Any gaps in access or evidence belong in the findings.
The deliverable
A short decision memo for the person responsible for the system:
- Current picture: the parts of the system relevant to the decision and the evidence reviewed.
- Options: improving the current system, changing a component, or migrating, where each is a credible choice.
- Tradeoffs: cost assumptions, operating burden, dependencies, and risks that need attention.
- Next step: a phased recommendation, with the questions to answer before making a larger commitment.
Cost estimates would include their assumptions and uncertainty. The memo is useful when it lets the owner explain why a choice is worth making.
Where the scope ends
Implementation, production changes, and migration execution would be separately agreed work. A review does not promise savings or a successful migration.
Bring the system’s purpose, the change you are considering, and what has made the decision difficult. We can use that to decide whether a review is the right first engagement.