chennai Banner

Verification Vs Validation

Discuss PMI-PBA® doubts, tips and lesson learned. Master the art of Business analysis with iZenBridge
nagasowmya123
Participant
Participant
Posts: 66
Joined: Thu Feb 11, 2016 11:05 am

Verification Vs Validation

Postby nagasowmya123 Wed Mar 16, 2016 12:43 pm

In software development life cycle, the verification will be done by the business analyst or solution provided persons and validation will be done by the quality people which are simply called as testers in IT. Please correct if I am wrong with the statement.
seema.sonkiya
Expert
Expert
Posts: 1606
Joined: Fri Jul 11, 2014 11:57 am

Re: Verification Vs Validation

Postby seema.sonkiya Fri Mar 18, 2016 10:33 am

Yes, verification of solution can be done by the business analyst and the validation can be by quality people or testers. Involvement is dependent on the business analysis plan. In exam, if referring the business analysis plan option is there, it is best to select. We have to choose the best option in the exam.

Verification and Validation of Solution are not described in detail in Business Analysis Practice Guide, you need to refer PMBOK for the same. For the exam, videos are more than sufficient.

Chapter 12 has the video for Validate Scope. The goal of this process is to get the acceptance of deliverables. The input of this process is Verified deliverables (Verification of Solution). Verification is done by the Control Quality process (described in chapter 14).
Yes, Testers can also do validation to see the deliverable from the eyes of actual users. Involvement is depend on the plan.
For more details on validation Vs Verification , you may refer blog: http://www.izenbridge.com/blog/differen ... alidation/

In Business Analysis Practice Guide, the verification and validation of requirements are described in detail: Verification of requirements is done (But not limited to)for un-ambiguities, consistencies and precision. Inspection and Peer Review tools can be used in verification.

Business Analysts and testing resources could be great reviewers in verification of requirements.

Validation of requirements can be done by Delphi, weighted ranking method and multivoting tools. Validation of requirements ensures that requirements will solve the business stakeholders problems. Business Stakeholders could be customer or End Users (But not limited to).

Chapter 5 has video for the validation and verification of requirements.
akanksha.ashar5
Participant
Participant
Posts: 53
Joined: Fri Jul 29, 2016 4:06 pm

Re: Verification Vs Validation

Postby akanksha.ashar5 Fri Dec 02, 2016 9:55 am

"Chapter 12 has the video for Validate Scope. The goal of this process is to get the acceptance of deliverables. The input of this process is Verified deliverables (Verification of Solution). Verification is done by the Control Quality process (described in chapter 14). "
In extension to above stated sentence -

Does it means that Validation of Solution is done after Verification of Solution. It is a continuous process as Verification is done in Monitoring and Controlling Process Group - Control Quality Process?

Also, confirm whether Requirement validation follows Requirement Verification as per PMI - pBA Practice guide.

PLease clarify on above queries. Thanks.
seema.sonkiya
Expert
Expert
Posts: 1606
Joined: Fri Jul 11, 2014 11:57 am

Re: Verification Vs Validation

Postby seema.sonkiya Sat Dec 03, 2016 1:45 pm

Requirement Verification & Validation is an Iterative Process. After verification of requirements, validation can be done and vice versa.
Requirements characteristics help in verification of requirements. Validation needs engaging business stakeholders. Please go through the PPT available in chapter 5 item 26.

PMBOK Validate Scope process emphasizes on final acceptance of deliverable (which could be the solution also), before that which may have many rounds of requirement verification and validation.

Return to “PMI-PBA Open Forum”

Who is online

Users browsing this forum: No registered users and 2 guests