Guide: phase 5, Go live

You run the cutover, retire the old system, hand over to support and close the project. The Go live complete gate closes the phase.

This page applies to the Go live stage.

Project manager guide

Switch to IFS Cloud, give support a working handover and close the project with every open item owned.

  1. Run the cutover.
    • Do now: Follow the approved cutover plan task by task. Record the real times and the go or no-go decision.
    • Why: Before the point of no return you can roll back. After it you cannot.
    • The app checks: Users are released only after the production backup is confirmed.
    • Next: Start hypercare.
  2. Run hypercare and hand over.
    • Do now: Open Handover. Fill the checklist, record the hypercare duties, hold the handover meeting and list the known defects and workarounds.
    • Why: Support takes over a system it did not build. It needs the full picture.
    • The app checks: The support manager, the customer project manager and the system owner must all accept. Support can also list what is missing.
    • Next: Switch off what was decided.
  3. Connect interfaces and retire legacy systems.
    • Do now: Check that every interface is live and that each old system is handled as decided.
    • Why: A forgotten legacy system keeps running and keeps costing money.
    • The app checks: The interface register shows the status of each interface. Cutover actions come from your earlier decisions.
    • Next: Set the update policy.
  4. Set the update policy and sign off the data.
    • Do now: Open Updates and agree the update policy for future releases. Collect the final sign-off of the data migration.
    • Why: The system stays current only if someone owns the update rhythm.
    • The app checks: The gate page shows whether the update policy is agreed. The data owner signs each data group.
    • Next: Capture the lessons.
  5. Record lessons learned.
    • Do now: Open Closure. Write what to repeat and what to change. Name the cause and the fix.
    • Why: Specific lessons help the next project. Vague ones do not.
    • The app checks: No risk or issue should stay without an owner outside the project.
    • Next: Close the project.
  6. Approve the closure and close the gate.
    • Do now: Submit the closure. Then open the Go live complete gate, link the evidence and request the decision.
    • Why: The closure releases the team and passes the benefits to the customer sponsor.
    • The app checks: The supplier project manager, system owner, sponsor and steering group chair approve in turn. A closed project cannot be changed until the closure is reopened.
    • Next: The system moves to the maintain stage.

Related topics

Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.

Last updated: