S
sathulan
Comparing ISO with PMBOK
Hi all:
I have 2 questions and since I am from the software domain, I would like to restrict the focus of these questions/responses to software development.
1) PMBOK (Project Management Body of Knowledge, www.pmi.org) describes quality control and scope verification as-
Quality control: analysis of the correctness of work
Scope verification: is concerned with customer acceptance of the project efforts
Would it be correct to say that verification as defined in the ISO9000:2000 is what the PMBOK describes as Quality control above and similarly, is "Validation" as defined in the ISO vocabulary what is referred to as "Scope verification" by the PMBOK above?
2) A question on risk management: should constantly changing scope of work (due to changes in requirements by the customer) be treated as a risk?
As I understand, risk is something with an element of uncertainity about it. When it is known that a particular customer *will* change requirements frequently, is that to be treated as a risk - since there is no uncertainity here.
Would appreciate inputs from the experts out there.
Thanks
Athulan
Hi all:
I have 2 questions and since I am from the software domain, I would like to restrict the focus of these questions/responses to software development.
1) PMBOK (Project Management Body of Knowledge, www.pmi.org) describes quality control and scope verification as-
Quality control: analysis of the correctness of work
Scope verification: is concerned with customer acceptance of the project efforts
Would it be correct to say that verification as defined in the ISO9000:2000 is what the PMBOK describes as Quality control above and similarly, is "Validation" as defined in the ISO vocabulary what is referred to as "Scope verification" by the PMBOK above?
2) A question on risk management: should constantly changing scope of work (due to changes in requirements by the customer) be treated as a risk?
As I understand, risk is something with an element of uncertainity about it. When it is known that a particular customer *will* change requirements frequently, is that to be treated as a risk - since there is no uncertainity here.
Would appreciate inputs from the experts out there.
Thanks
Athulan