Post Launch

Validate Rules of Engagement

Once launch has been completed, further actions will no longer be part of the initial implementation, but will involve separately chargeable follow up work.

At this point it will be appropriate to validate the rules of engagement with respect to billing.

As pointed out in Customer Services and Support Guide.

Check if there are any variations from default.

Determine who will be responsible for approving any chargeable work.

Commission Test and Populate Test Environment

Create new test environment based on live config data.

Better to do this after launch as the configuration will mirror live, without having to keep two systems in sync manually during the pre-launch phase.

LINK to HOWTO on this.

Customer Summary Wiki Page

The customer summary wiki page should be updated to reflect the current state.

Not sure if this is required.

Problem Escalation Rules

Here we could do with a flow diagram which describes who should be contacted for different types of problems.

LINK to example diagram.

Post Launch Functional Follow Up

The system should be given an opportunity to bed in, with users getting used to the system, and dealing with corner cases which inevitably arise.

Within 2 to 4 weeks after launch, is appropriate to follow up with a functional review:

what is working well
what is not working so well
any areas that are likely to require change/improvement

At this point, a program of further improvements can be initiated, if appropriate.