Schedule doubt

Submitted by jason on Fri, 08/08/2008 - 14:52

Hi Forum,

 Here is a question I am not sure what is the reason for the answer. I got this question from my trainer who taught me 1 year ago and I forgotten the rationale for the answer.  Hope you can help me.

 

If dependency was discovered during project execution, what is the best thing to do?

a. redo sched devt

b. Call a team meeting to discuss options like crashing or fast tracking are possible solutions to meeting the original schedule

c. Call a meeting of stakeholders and communicate the schedule risks.

Please let me know your answer and why you chose it.

 

regards

Jason 

 

Forums: 
PMP / CAPM exam Question bank
  • Log in to post comments
  • 2541 reads
admin's picture

admin

Tue, 08/12/2008 - 06:37

The answer would be c. This would be the first step, since a dependency may or may not have a schedule impact, so you must communicate to all stakeholders first about the schedule risk.

Crashing and Fast Tracking will only be required if the Activity is on Critical path

zerry.siddhu

Wed, 09/17/2008 - 13:34

First thing you do is to communicate the risk with stakeholders and sponsors if you find any change in the schedule.

 

Compression and fasttraking are the techniques that you will use afterwards, to achieve the scheduled end date.

crabapple

Tue, 08/12/2008 - 17:24

definitely C!

SRCMrClark (not verified)

Mon, 10/20/2008 - 07:09

The first thing to do would be to assess whether or not the newly discovered dependancy actually affects the schedule and if so how.  Next you'd discuss possible options with the team (and yes, crashing/fast-tracking may be options since the question doesn't specify whether or not the dependancy is on the CP or not).  Then and only then should you call a stakeholder meeting.

Rationale:  You wouldn't go running to the stakeholders until you fully assesed the risk AND have formulated courses of action - both of which you'd (of course) do with your team. 

zerry.siddhu

Fri, 11/07/2008 - 18:36

Here is the order of steps you do:

* Analyze the impact on triple constraint.

* discuss with stakeholders (internal buy in)

* Schedule compression to find possible solutions

 

Since we dont have the option of Analyze the impact, I will choose C !!

Adil

Fri, 12/05/2008 - 12:01

I think that all answers  (a, b and c) are just given by our friend who made this question, for sure in any test exam or exam  you will not find such answers.

 any way the nearest answer is B because we have first to evaluate before communicating to stackholders (what we are going to say and communicate to stackholdres before avaluating)

lalantha

Mon, 12/22/2008 - 05:20

If you meet with the stakeholders they are going to ask you what you plan to do.

So, you have to be prepared, perhaps after consulting the rest of the team.

The answer should be B.

George

Mon, 12/29/2008 - 08:51

In order to check impact on schedule I think PM has to redo schedule development considering the missed dependency (choice a). Please note that impact could be zero (adjusting some activity/ies lag time(s)).

In case schedule is definitely to be affected, next step would be to get stakeholders buy in, in order to take action like applying a schedule compression technique and confront the problem (next steps b and c).

So I'd go with a. 

Cheers and Bye,

George 

 

vkajith

Wed, 12/31/2008 - 10:23

The first step to be followed after finding out the dependancy is to Analyse the effect.

Dependancy affects the schedule and hence the best way to analyze the risk is to Redo the Schedule (to analyze whether the schedule will be changed). Option A is not asking to Change the Schedule, which would have been a wrong answer.

 Once the PM redo the schedule development, he can determine whether changes are necessary and he can follow other steps.

Best Regards
Ajith