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
The answer would be c. This
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
C for sure
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.
definitely C!
I'd say "B"
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.
Ans is C
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 !!