Decide on preliminary acceptance
Preliminary acceptance creates the basis for commissioning the system with acceptable risks.
Preliminary acceptance takes place before deployment and commissioning of the system. Quality assurance measures such as tests and inspections are carried out beforehand. Preliminary acceptance gives users, developers and operators the assurance that the transfer from the old to the new system state will most likely be successful.
Preliminary acceptance is planned early by all those involved. The acceptance criteria are agreed jointly in the process. If a system is procured, this takes place when the contract is concluded between the organizations involved in the project. If a system is developed, the acceptance criteria are determined at the same time as acceptance of the system requirements and system architecture.
Determine the organization and general conditions for preliminary acceptance
Add further criteria to the preliminary acceptance checklist
Prepare preliminary acceptance in technical and organizational terms
Perform preliminary acceptance and record findings
Analyze and classify findings (e.g. by defect category, new requirements)
Decide on preliminary acceptance and the next steps
|Module||Task||Task responsibility||Outcome||Involved in creation of outcome|
|Deployment organization||Decide on preliminary acceptance||Project manager||Acceptance report||Operations manager, User representative, Application owner, Developer, Quality and risk manager|
|Decide on preliminary acceptance||Project manager||Checklist|
|Decide on preliminary acceptance||Project manager||Project decision management & execution||Quality and risk manager|