In version 5 of the PMBOK guide, there was great attention paid to the difference between "Verification" and "validation." Verification was done by the project team and validation could only be done by the end-use.
At the time, this was to put the PMBOK's definitions more inline with other ANSI standards such as Systems Engineering.
Have things changed in version 6? The terms seem to be nearly interchangeable in Version 6. There's no clear distinction drawn between validation and verification Saving Changes...
Interesting observation. For me you or someone from the project team can verified that it it properly done. THe client or end-user can validate in the approval process.
PMBOK rev6 is so Agile! ;-) Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I do not remember what version 5 said but if the end-user is part of the project team then validation is performed for the project team. In fact, it will depend of your life cycle process.
In version 6 there were lot of debate about the right use of "verification" and "validation" tems. I was one of the people that debate on that, but I have not obtained to much success. My argument was aligned with this: in quality field you will find that "verification" belongs to quality assurance while "validation" belongs to quality control. You will find the definition into the glossary of terms but in my personal opinion is not aligned with the general agreement including asociations like ASQ. The point is when you read the new PMBOK some things are confused, for example when you read scope validation.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Apr 03, 2018 11:17 AM
Replying to Sergio Luis Conte
...
I do not remember what version 5 said but if the end-user is part of the project team then validation is performed for the project team. In fact, it will depend of your life cycle process.
In version 6 there were lot of debate about the right use of "verification" and "validation" tems. I was one of the people that debate on that, but I have not obtained to much success. My argument was aligned with this: in quality field you will find that "verification" belongs to quality assurance while "validation" belongs to quality control. You will find the definition into the glossary of terms but in my personal opinion is not aligned with the general agreement including asociations like ASQ. The point is when you read the new PMBOK some things are confused, for example when you read scope validation.
Verification and validation are independent procedures that are used together for checking that a product, service, or system meets requirements and specifications and that it fulfills its intended purpose.
These are critical components of a quality management system such as ISO 9000. The words "verification" and "validation" are sometimes preceded with "independent", indicating that the verification and validation is to be performed by a disinterested third party.
The PMBOK guide, a standard adopted by IEEE, defines them as follows in its 4th edition:[2] "Validation. The assurance that a product, service, or system meets the needs of the customer and other identified stakeholders. It often involves acceptance and suitability with external customers. Contrast with verification."
"Verification. The evaluation of whether or not a product, service, or system complies with a regulation, requirement, specification, or imposed condition. It is often an internal process. Contrast with validation."
I think our version 6 has drifted from our alignment with other ISO standards. Saving Changes...
Lanka Van DortHead of Software Engineering| Endress+Hauser Optical AnalysisAnn Arbor, Mi, United States
In the V-Model, Verification is the LHS of the V and Validation is on the RHS.
Simply put Verification ensures Software product implements all the documented software requirements. Validation is to determine the software product satisfies its intended use. In other words, the SW satisfies all indicated user needs.
...
1 reply by David Maynard
Apr 03, 2018 11:40 PM
David Maynard
...
Hello Lanka,
For everyone else, here's an image of the System Engineering V model Lanka mentions.
It clearly shows that subsystem verification takes place prior to system validation. That concept was lost in the move from PMBOK V5 to V6. Verification and Validation appear to be used interchangeably in PMBOK V6.
Verification may be done by an independent source because it is aligned with quality assurance. Validation surely has to be performed by the customer. Saving Changes...
It was clearly stated that way in version 5 of the PMBOK guide and is stated that way in most (all?) other ANSI standards, but it doesn't appear that clear-cut in PMBOK guide version 6. We (PMI) seem to have drifted off the mark here.
9.5.1.3: "Performance reports that can help with project team management include results from schedule control, cost control, quality control, and scope validation."
"Validation. The assurance that a product, service, or result meets the needs of the customer and other identi?ed stakeholders."
X5.2: "Validation and control. Does the organization have existing formal or informal validation and control-related policies, procedures, and guidelines?"
Even Section 5.5.2 is called: "5.5.2 VALIDATE SCOPE: TOOLS AND TECHNIQUES"
So, I think that VERIFY and VALIDATE scope have been mingled in version 6 and no longer agree with the systems engineering ANSI standard. Saving Changes...
I do not remember what version 5 said but if the end-user is part of the project team then validation is performed for the project team. In fact, it will depend of your life cycle process.
In version 6 there were lot of debate about the right use of "verification" and "validation" tems. I was one of the people that debate on that, but I have not obtained to much success. My argument was aligned with this: in quality field you will find that "verification" belongs to quality assurance while "validation" belongs to quality control. You will find the definition into the glossary of terms but in my personal opinion is not aligned with the general agreement including asociations like ASQ. The point is when you read the new PMBOK some things are confused, for example when you read scope validation.
In the V-Model, Verification is the LHS of the V and Validation is on the RHS.
Simply put Verification ensures Software product implements all the documented software requirements. Validation is to determine the software product satisfies its intended use. In other words, the SW satisfies all indicated user needs.
Hello Lanka,
For everyone else, here's an image of the System Engineering V model Lanka mentions.
It clearly shows that subsystem verification takes place prior to system validation. That concept was lost in the move from PMBOK V5 to V6. Verification and Validation appear to be used interchangeably in PMBOK V6. Saving Changes...
Thank you for all valued info from Sergio mentioned about ASQ and David mentioned IEEE and I have according to ISO 9001 Design Verification and Design Validation
These two steps are distinctly different, and important in a good design process. One step is used to make sure that the design has addressed every requirement, while the other is used to prove that the design can meet the requirements set out for it.
Each of these steps is important in the design process because they serve two distinct functions. Verification is a theoretical exercise designed to make sure that no requirements are missed in the design, whereas validation is a practical exercise that ensures that the product, as built, will function to meet the requirements. Together, they ensure that the product designed will satisfy the customer needs, and the needs of the customer are one of the key focuses for ISO 9001 and improving Customer Satisfaction Saving Changes...
Community Champion
