Final Product Acceptance
What
The event where the system-to-be has met the product accept specifications and the customer accepts the delivery of the system according to the contract.
How
The dish
Product Accept
Ingredients
- Product Accept Specification
- Development Plan
- Deployment Plan
- Quotation
- Final Contract
Process
The system-to-be is being deployed according to the deployment plan, and the product accept specifications are tested and verified. If the deployed system fails to meet the accept specifications, you need to make a list of the deficiencies specifying the problem and then decide whether the problem will stop further deployment or if the problem can be fixed later.
When the entire system is deployed and has been tested according to accept specifications, when the list of deficiencies is empty and verification completed, the product accept is due to take place.
The product is accepted when the customer signs a product accept declaration and accepts the product according to the quotation and the final contract.
Why
Just as the initial customer contact is very important for the success of the project, so is the product accept event. Here you actually feel the success rate. If both the developer and the customer are satisfied, the task is carried out well. If not satisfied, you have the scene for a lot of frustration!
The customer will not accept the product because his or her wishes and expectations have not been met. Consequently, the customer will not pay the bill and the developer has to hire lawyers. Another scenario is that the developer has to make many corrections if the quotation and product accept specifications are incorrect. This means additional costs in terms of time and money.
To prevent frustration, loss of confidence, loss of reputation, time and money, you have to follow the four phases of the embedded unified development process carefully and at all times during the project, remember to involve the customer.
