1. Project quality management identifies the quality requirements and standards necessary to satisfy and comply with the project requirements.

2. Quality Control is the mean to review and record specific quality process in order to assess performance and recommend changes.

3. Quality assurance process is auditing the quality process in a routing basis.

4. Grade refers to the features or characteristics of a product. The features and the end product could be of high or low quality depending on how well it complies with the requirements of the standard and fit its intended purpose.

5. The quality of an element can be definite base on its function, output, performance, and reliability.

6. The function (also known as features or capability) is the intended used of the end product.

7. Outputs (tangible or not) or products should be tested again on the required standards and the alignment with its function to determine the degree of its quality.

8. Performance is the result of the evaluation of the product against the understanding desire output. It includes two factors; (a) reliability, the ability of a product or service to perform as expected under normal conditions, without unacceptable failures. And (b) maintainability, the intended performance of the part(s) over a specific period of time.

9. Quality program information should include Goals, Process, Standards, Activities, Tools, Rolls and Responsibility.

10. The quality assurance plan considers reviewing and gathering internal and external quality data, document changes and why they are done, utilizing the approval process, the use of an action log, and consider the relation of the iron triangle… Furthermore, it considers deliverable, time, and prototyping, among others.

11. The Quality Function Deployment (QFD) or House of Quality, high light customer wants, propose potential solutions, and identify matching factors.

12. Testing & Action items should follow business requirements and the test plan. It should apply to 1) Unit test 2) Integration test 3) System testing and 4) User acceptance test.

13. The environment testing and test team is fundamental– Manager, tester, SMEs, and Business Analysis are an all-important parts of a test team.

14. Some practical quality tools are: Root cause analysis, Establishing true errors, Establishing patterns, Final double check, Process verification, Output verification Change confirmation, Inspection.

15. Review all change requests with your client to ensure agreement about maintain, quality, budget and time. All changes on the process or end-product should improve deliverables.

16. Make sure you have a good project change management process and early
define success and schedule testing with the client.

17. Spend more on appraisal and prevention activities reduce the cost of Internal and external failures.

18. Project success is measured in terms of how well a project meet budgetary, schedule, and performance requirements.

19. Pareto principle (also known as the 80/20 rule) stated that in general, the majority of problems are triggered by a relatively small number of causes. The most cost-effective approach to quality assurance is to attend to those problems that have the most serious impact on quality failures.

20. The objective of modeling is not to create perfect models but to generate data that will result in a high-quality final product.