Today, I will discuss verification vs validation
验证和验证是项目管理中的两个重要术语。因为它们看起来非常相似，所以很容易让他们感到困惑。
These are important concepts, and any PMP aspirant needs to understand them well.
虽然这个话题不一定从中PMP exam作为项目经理的观点，您必须能够区分这些术语。
让我们开始吧。
验证与验证
We will start with verification.
Verification
验证是关于正确构建产品，确保其满足所有既定质量要求，并如下所述。
验证是一个客观过程。所有质量要求都必须有充分的记录，以进行适当的测量和分析。
例如，假设您正在开发手机。您已经进行了市场研究，并收集了有关所需功能的所有信息。您制定了制造产品，完成所有要求并相应开发产品的计划。
Now, the production process has started. You carry out an inspection to ensure that everything is going according to plan.
If the product meets requirements, this means it has been verified.
Verification ensures that the product is of high quality, and it is useful in making sure the product is error-free. This is a thoroughly objective process; however, this does not mean the product will meet customers’ requirements, which is where validation comes in.
Validation
Validation is about making sure you have developed the correct product and that it meets customers’ requirements.
验证是一个主观过程。它向您展示了产品满足客户需求的能力。建模，仿真和用户评估是一些有助于无效过程的技术。
例如,假设您正在开发一个cell phone for your customers. You have conducted market research and determined what features the item should have. Then you started the production.
However, when the cell phone is finally launched, it does not get the expected market response. Eventually, it fails.
在这种情况下，您会说该产品无法得到验证，因为它无法满足客户的期望。验证与产品测试有关，这是一个根本主观的过程。
Difference Between Verification and Validation
Verification ensures that products meet the specifications, whereas validation ensures that those specifications meet customer requirements.
A few differences between verification and validation:
- Verification evaluates the process and the product in development, while validation evaluates the product itself.
- Verification helps the product be built the right way. The objective of validation is to build the right product.
- Inspection and document review are verification tools. Validation activities include testing the product.
- The project management team performs the verification process while the client or customer performs validation.
It is possible for the product to pass verification but fail validation.
In the example provided, you can see this; the company developed a cell phone that passed through the verification process. However, when they launched it, the customer response was not positive. The product failed, meaning it can’t be validated.
概括
Verification and validation are independent procedures. The project manager uses these processes to ensure they have correctly built the right product. Verification is about conformance to specifications, an internal process. Validation is about customer expectation, and it is often an external, subjective process. Verification comes before validation.
I hope this discussion on verification vs validation has been helpful. Please share your experience with using these processes in the comments section.
验证是关于产品的，而验证与该过程有关。您如何看待我对本文的摘要？
In verification you check if the product is developed as designed and requested by stakeholders.
Good example with the cell phone. Take the Microsoft Office Phone for example.
The project could be successful in terms of building the phone, but customers did not like the phone and it was not supported; therefore, as a product, it failed.
So, the phone was build correctly; meaning the phone was verified. The phone was a commercial failure, therefore it was not validated.
The subcontractor who built the phone had a successful project. The customer who had a failed product also had a successful product creation project, but a failed product lifecycle experience.
The point of confusion could be: don’t confuse the product lifecycle failure with the project success.
Do I have this correct?
Well said David.
Terms to be truly useful need to be have singular understanding when used. For validation and verification we have run into issues with interpretation by individuals familiar with systems engineering, but as much with people not familiar w/SE since they typically don’t have a clue.
At times we overthink a definition to the point the definition becomes confusing to the majority of individuals that hear the term. A good example is ‘Risk’. A layman using English langue hears the term ‘Risk’ and thinks something bad can happen. Someone following PMI terminology hears the term ‘Risk’ and ‘may’ think ‘threats & opportunities’.
So, with V&V terms, some additional work is needed to either make them very clear and distinguishable, or use terms no one knows and define them.
比尔说。
Verification
Verification is about building the thing in right way. <— huh? Building the thing in right way is not grammatically correct.
Corrected.
您能告诉我主观过程与客观过程之间的区别吗
在客观的过程中，您有可衡量的标准，在主观过程中，它们开放讨论并取决于当事方。
And also how configuration mgmt. differs from project scope mgmt. as both addresses the actual result, product or service of the project.
嗨，法哈德（我希望您不会对很多问题感到无聊）变更管理与执行集成变更控制有何不同？
Thank you again
嗨法赫德,继续前面的问题来回m me on validated changes question, in 4.4.1.1 on page on.90 it says ” approved changes that results from the Perf. Inte. Change Control process require validation to ensure that the change was appropriately implemented. A validated change provides the necessary data to confirm that the change was appropriately executed.” To me it seems that an approved change request gets implemented through Direct & Manage project work & through Control quality deliverables ( which is the resultant of either first time work or approved change request work) gets validated & also the control quality validates that the approved change to the original plan worked well, delivered the validated result & hence should update proj. mgmt. plan & proje docu & should be archived as best practice for future references. Did I understand the cycle correctly? Pl. share your though.
Hi Fahad, could you pl. shed more light on Validated changes which is an O/P from Control Quality process & I/P to M & C Process. As per PMBOK page 262 it says that ” any changed or repaired items are inspected & will be either accepted or rejected before notification of the decision is provided. Rejected item may require rework.” By the definition it should go to validate scope (same as verified deliverables) unless if the only difference between verified deliverable & verified changes is the former deals with the result of the project & later deals with processes?? But once again the doubt is the definition itself which as above says that ” any changed or repaired items are inspected’.
Kindly share your thoughts at the earliest.
Hi Fahad,
You have not replied to this important question. I too have questions regarding Validated Changes. Your thoughts and explanations would be much appreciated.
Anil
我不明白上述问题。你有什么疑问？
感谢您的解释。快速问题：
1. Verification – control quality?
2. Validation – Scope management?
3.是否在验证之前进行验证或与验证同时执行？
1) Verification include quality control and quality assurance.
2) Validation include scope management plus quality assurance and control.
3) You can say, these are compliment to each other.