MENU
Which of the following is the LEAST effective way to influence the factors that create changes to the cost baseline?
Suggested Answer: B
Get Premium PPM-001 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
47 comments · newest first
JU
Justa
11 months ago
Option A seems more productive than D for sure.
TA
Tayna
11 months ago
Wait, are we really saying no changes at all? That seems risky.
DA
Daniel
11 months ago
Eliminating scope might not solve the root issue.
CO
Cordelia
12 months ago
Totally agree, cutting off changes won't help.
NA
Nan
12 months ago
I think option D is the least effective.
HE
Hester
12 months ago
I vaguely recall that explaining the negative impacts of changes is usually a good strategy, so maybe B isn’t the least effective?
MO
Moira
1 year ago
I feel like option A could be effective, but I’m leaning towards D as the least effective since it doesn't address the root cause of changes.
FL
Fletcher
1 year ago
I remember a practice question where we discussed the impact of changes on the cost baseline, but I’m not sure if eliminating scope is really the best approach either.
GL
Glenn
1 year ago
I think option D might be the least effective because just telling stakeholders no more changes can create frustration.
HY
Hyun
1 year ago
This is a tricky one, but I think I've got it. Eliminating the scope causing the most changes seems like the least effective way to influence the factors creating cost baseline changes. I'll go with that option.
HI
Hildegarde
1 year ago
I've got a strategy - I'll eliminate the obvious wrong answers first, then focus on evaluating the remaining options more closely. Explaining the impact of changes to stakeholders could be a good approach, but I'm not sure if it's the least effective.
LA
Lakeesha
1 year ago
I'm a bit confused by the wording of the question. Notifying stakeholders that no more changes will be allowed doesn't seem like the least effective approach to me. I'll need to re-read the options carefully.
OL
Olive
1 year ago
Okay, let's see. Reviewing the scope with the functional manager seems like a good first step to understand the drivers of change. Eliminating the scope causing the most changes could also be effective.
CH
Christa
1 year ago
Hmm, this is a tricky one. I'll need to think carefully about the different options and how they might impact the cost baseline.
LA
Lashon
1 year ago
This seems straightforward - I'd go with options A and D to automatically generate work orders with a 14-day generation horizon to meet the inspection requirements.
RO
Rozella
1 year ago
Okay, let's see. I think A and B are both true, but I'm not sure about the others. I'll need to review my notes on DSCP and forwarding classes.
LA
Lashaun
1 year ago
Option D? More like 'Don't notify the stakeholders and hope the changes just go away.' That's not how project management works!
ED
Edwin
1 year ago
Option A seems like a logical step. Reviewing the project scope with the functional manager responsible for the most changes could help identify the root cause and address it effectively.
WA
Wayne
1 year ago
Hmm, Option B sounds like a good approach. Explaining the impact of changes to the stakeholders could help them understand the consequences and potentially reduce the number of requests.
VI
Vilma
1 year ago
User 3: Yeah, communication is key in managing changes to the project scope.
CA
Carylon
1 year ago
User 2: I agree. It can help them understand the consequences and think twice before requesting changes.
AS
Ashton
1 year ago
User 1: I think Option B is a good idea. It's important to explain the impact of changes to stakeholders.
DA
Darci
1 year ago
I think Option C is the way to go. If the scope is causing the most changes, it's better to eliminate that part of the project altogether.
WI
Wilda
1 year ago
Option D seems too extreme. We should try to find a balanced approach that addresses the changes without completely shutting down the project.
FE
Felix
1 year ago
Option D? More like 'Don't notify the stakeholders and hope the changes just go away.' That's not how project management works!
CA
Caprice
1 year ago
Option A seems like a logical step. Reviewing the project scope with the functional manager responsible for the most changes could help identify the root cause and address it effectively.
RI
Ricki
1 year ago
D) Notify all stakeholders that no more changes will be allowed.
SH
Shelton
1 year ago
C) Eliminate the scope causing the most changes.
RO
Rosita
1 year ago
B) Explain to those requesting changes the negative impact of change to the project.
RU
Ruth
1 year ago
C) Eliminate the scope causing the most changes.
EL
Elbert
1 year ago
B) Explain to those requesting changes the negative impact of change to the project.
DA
Danica
1 year ago
A) Review the project scope with the functional manager responsible for the greatest number of requested changes.
LO
Lorrine
1 year ago
A) Review the project scope with the functional manager responsible for the greatest number of requested changes.
YO
Youlanda
2 years ago
Hmm, Option B sounds like a good approach. Explaining the impact of changes to the stakeholders could help them understand the consequences and potentially reduce the number of requests.
JU
Julio
1 year ago
I think that could cause resistance from stakeholders, it's better to communicate the impact first.
TY
Ty
1 year ago
But what about Option D? Would it be effective to just stop all changes?
EM
Emmett
1 year ago
I agree, stakeholders need to understand the impact of their requests.
AL
Alpha
1 year ago
Option B does seem like a good way to handle changes.
KR
Kristofer
2 years ago
I think Option C is the way to go. If the scope is causing the most changes, it's better to eliminate that part of the project altogether.
NE
Nelida
2 years ago
I believe C) Eliminate the scope causing the most changes is also not very effective. It's better to address the root cause of changes.
ME
Melda
2 years ago
I agree with Joaquin. It's important to communicate the negative impact of changes to stakeholders.
GL
Glory
2 years ago
Option D seems too extreme. We should try to find a balanced approach that addresses the changes without completely shutting down the project.
TA
Tatum
1 year ago
Option D seems too extreme. We should try to find a balanced approach that addresses the changes without completely shutting down the project.
RO
Rosenda
1 year ago
C) Eliminate the scope causing the most changes.
MA
Margarett
1 year ago
B) Explain to those requesting changes the negative impact of change to the project.
IL
Iluminada
1 year ago
A) Review the project scope with the functional manager responsible for the greatest number of requested changes.
JO
Joaquin
2 years ago
I think the least effective way is D) Notify all stakeholders that no more changes will be allowed.