Goal for the sprint:

The main goal is to stabilize the solution and hand it over to the customer. Fixing the bugs that haven’t been discovered during the UAT.
Transition to support.

IMPORTANT - SOC compliance requirement

When the project is closed, the customer takes full and sole ownership of user management.
That means the following:

• No Pricefx person is authorized for creating and managing users on production partition.

• A limited number of Partner/Pricefx resources have production access: we should only have this to look into reported issues.
  This should only be a couple of users, e.g. the SA, CE and QA, and only with a business user profile.

• There is a plan to remove all authorisations from all Partner/Pricefx resources in PROD (so that Partner/Pricefx can't be blamed of any wrong doings in the customer's PROD system).

These points above only apply to the productive system - QA, DEV, UAT are not impacted.

Actions:

• Document all bugs and changes in Jira.

• Align with CSM on Project Handover.

• Hand over user management to the client and ensure no Partner/Pricefx resource has access to user management in PROD.

• Clean up the Pricefx user accounts on PROD.

• Update all project information in Project Confluence page (see how to here).

• Provide CSMs information for their Go-live presentation.

• Project retrospective.

• Technical retrospective.

• Project Documentation - create project documentation as described in the artefacts section below, and have it reviewed by the PM Competency Lead.

• Partner/Pricefx PM is accountable for all the items above actions but can delegate.

Artefacts:

1. Project documentation

2. Go-live presentation describing support system process, reaching established success metrics, and next steps (owned by CSM)

3. https://pricefx.atlassian.net/wiki/spaces/CUST/pages/2088699669

4. Project Acceptance protocol