Use this guide to prepare a scope or compare proposals. It describes an approach to evaluation, not results from a MENTARA client engagement.
Buyer guides
Plan the first release of a legacy modernisation project
Define a useful first software release with clear dependencies, acceptance criteria, testing, rollback and operational ownership.
Planning resource
02
Choose a bounded business capability
Identify a capability whose behaviour and dependencies can be understood and tested. It should produce an observable benefit without requiring the entire legacy application to be replaced first. If no safe boundary is apparent, make discovery the first deliverable.
03
Map the release boundary
- Users, transactions and data covered by the change.
- Upstream and downstream systems, including batch jobs and manual handoffs.
- Ownership of records while the old and new paths coexist.
- Availability, access, performance and recovery requirements.
- Conditions for retiring the old path and retaining any required records.
04
Write the release plan
01 Establish current behaviour
Document representative journeys, exceptions and data outputs. Identify unknown behaviour that must be investigated before changing it.
02 Agree acceptance
Define functional outcomes and operating constraints with the receiving team. Include data reconciliation and error handling.
03 Prepare release and rollback
Assign cutover decisions, observation windows and rollback conditions. Test the plan in an appropriate environment.
04 Confirm ownership
Name the team that will monitor and support the release. Transfer runbooks and known issues alongside the software.
05
Check that the increment stands on its own
Illustrative example: extracting a reporting feed may be useful if it reduces a specific manual step and has a stable data contract. It is not a useful independent release if every downstream report must also be rebuilt before anyone can use it.
Ask what happens if the next phase is delayed. The first release should remain supportable, with its costs and temporary dependencies understood. A small release still needs appropriate testing and security review.
06
Explore the relevant service
Review the service scope and discuss the capability, responsibilities and first deliverable your requirement needs.
07
More buyer guides
Explore practical resources for planning software, platform, cloud, AI and workforce requirements.
One partner. One plan. Measurable outcomes.