Modernisation planning

Plan the changes before committing to delivery

Harten helps your team examine the options for an existing application and the work each option would require. The plan uses application findings and customer decisions, rather than assuming that a newer technology is the answer.

Decisions the plan needs to support

What to retain or change

Separate behaviour the organisation still needs from implementation choices that can be changed, and record who must confirm the difference.

Where to start

Identify a useful first piece of work, the dependencies it has and the questions that could prevent it proceeding.

How to check the result

Define the tests, reconciliation and operational review needed before a change is accepted or a migration progresses.

What the plan sets out

The proposed plan covers target-architecture options, delivery work, dependencies, migration and rollback, verification activities, risks and decisions. Timing scenarios show the effects of different assumptions; they are not committed dates or a staffing plan.

Illustration of application evidence informing a reviewable specification and modernisation plan.
Conceptual illustration. Customer requirements, constraints and review are needed before the proposed work is accepted.

Inspect the PRSD-IWS plan and delivery schedule

The public example includes architecture, change mapping, migration, verification and delivery sections. Its Gantt view lets you switch between low, central and high duration scenarios and inspect the dependencies behind the sequence.

Open the plan and Gantt view

Test the assumptions that could change the approach

A narrow feasibility exercise can answer an agreed technical question, such as whether a dependency prevents a proposed change or how a selected rule can be checked. The question, test and expected evidence are agreed before starting.

Business policy, production usage, budgets, team capacity and release windows are not established by source analysis alone. They must be supplied or reviewed by the people responsible. Larger prototypes and implementation are separately scoped.

Commission an assessment before delivery

The four-week engagement combines application recovery with customer review and agreed validation. It ends with the document set, recorded decisions, remaining gaps and recommended next steps, not a claim that modernisation is finished.

See the assessment scope and fee