Decide on acceptance
Acceptance concludes the provision of goods or services within the scope of the project and creates the basis for project closure.
Acceptance takes place between the project sponsor, developer or supplier and operator of the system. It regulates how outstanding obligations are to be handled and how the provision of goods or services is to be completed.
Acceptance takes place after the system has been launched and has been operational for an initial period during which any defects are identified.
Acceptance is planned early by all those involved.
If necessary, separate acceptance processes (between developer and operator, between developer and user, etc.) are carried out.
Determine the organization and general conditions for acceptance
Add further criteria to the acceptance checklist
Prepare acceptance in technical and organizational terms
Perform acceptance and record findings
Analyze and classify findings (e.g. by defect category, new requirements)
Decide on acceptance and the next steps
|Module||Task||Task responsibility||Outcome||Involved in creation of outcome|
|Deployment organization||Decide on acceptance||Project manager||Acceptance report||Operations manager, User representative, Application owner, Developer, Quality and risk manager|
|Decide on acceptance||Project manager||Checklist|
|Decide on acceptance||Project manager||Project decision management & execution||Quality and risk manager|