Best method to control changes on a project
Submitted by BalbirPashaPMP on Mon, 07/15/2013 - 16:31
Which of the following is the BEST method to contol changes on a project
a. Direct all changes to change control board.
b. Prevent changes from being made.
c. Look for sources of changes
d. Document the changes quickly when they occur.
Forums:
admin
Tue, 07/16/2013 - 03:22
Permalink
If you look at the source of
If you look at the source of changes then you can better control it. For eg: you see a lot of CRs and find out that source is from a given stakeholder who is himself not clear on scope. You manage the source and you can better control the changes
jvleminc
Wed, 07/17/2013 - 22:05
Permalink
B
I'd say B is the best answer; preventing changes would also include looking at potential sources of changes.
pmpnewster
Thu, 07/18/2013 - 01:37
Permalink
Prevent changes means
Prevent changes means stopping all changes... including genuine, beneficial ones. That's not what we want.
I'd go with C.
Regards.
jvleminc
Fri, 07/19/2013 - 14:05
Permalink
Hmm, ok, this is one of these
Hmm, ok, this is one of these interpretation questions. I didn't make "prevent" to mean "don't make any changes"; I interpreted it as preventing unnecesary changes...
With your interpretation, I'd go for A.
th9063
Thu, 07/18/2013 - 02:49
Permalink
I would say "c" but upon
I would say "c" but upon looking up Perform Integrated Change Control PMBOK 4 Page 93
Documenting the complete impact of change request
avonag
Fri, 07/19/2013 - 15:14
Permalink
It has to be one of these two
It has to be one of these two options. Remaining two can be ruled out.
a. Direct all changes to change control board.
c. Look for sources of changes
Now for a) you are leaving all the actions to the control board to do. In the case of c) you are proactively dealing with changes. This is one of the important goals in Monitoring & Control process - to make sure that the changes are beneficial and influence the factors around this.
Consider of a scenario that there are lot of changes in the project. Then the control board will not have time to just look at changes. If you were working on the source of changes, that condition will not arise.
That will make c) my answer.
vikula01
Fri, 07/19/2013 - 16:51
Permalink
option c
ok - change comes in -
I direct it to CCB - For approval
Document it - for records
prevent it - preventive action
Look for source - root cause analysis - I guess its option c -
ginumon
Fri, 07/19/2013 - 18:38
Permalink
Answer is C
Looking for the root cause of the change and correcting it is more important to prevent future changes.
BalbirPashaPMP
Sat, 07/20/2013 - 18:47
Permalink
Answer is C
Yes guys correct answer is C.
thanks for the discussion...
I was confused with option B and C.
Here is my understanding:
Why not A: You do not direct ALL the changes to CCB. PM has the authority to make decisions on some of the changes.
Why not B: Some changes can be beneficial fot the project so Preventing the changes is not a wise decision at times.
Why C: You can check wether the option availble is beneficial or harmful to the project. so checking for the cource is a better option.
Why not D: its ok if I dont write the explainination, its obvious.