The decision on acceptance concludes the provision of goods or services within the scope of the solution development and creates the basis for the decision on closure phase release. The solution, including the required documentation, is definitively transferred to the application organization and, where applicable, to the operating organization.

Acceptance takes place between the project sponsor and the developer or supplier and operator of the solution; in the case of a product, the operator is generally the user. Acceptance regulates how outstanding obligations are to be handled and how the provision of goods or services is to be completed.

Acceptance takes place after operational activation and after the solution or part of the solution has been operational for an initial period during which utilization can take place - e.g. according to the product concept - and any defects are identified.

Acceptance is planned by all those involved in a timely manner.

With the acceptance of the solution, the development/parameterization of the system, the development/adaptation of the service/product, or the implementation of the organization is definitively completed and the provision of goods or services within the scope of solution development is concluded.

If necessary, separate acceptance processes (between developer and operator, between developer and user, etc.) are carried out.

1. Organization activated
2. Operation activated
3. Product documentation
4. User manual

1. Determine the organization and general conditions for acceptance.
2. Add further criteria to the acceptance checklist.
3. Prepare acceptance in technical and organizational terms.
4. Perform acceptance process and record findings.
5. Make formal decision on acceptance and next steps.
6. Analyze and classify findings (e.g. by defect category, new requirements).

1. Acceptance checklist
2. Acceptance report
3. Acceptance milestone
4. List of management project decisions