Page 1 of 1

Fast Tracking

Posted: Thu Sep 14, 2017 12:02 am
by nazrulq
Q. Project Manager along with team member discuss about the fast tracking of the project schedule. To fast track which of the following statement are true:

1. Project has extra money in contingency reserve.
2. The project has high risk.
3. Activities have preferential dependencies.
4. Add resources to the activities to fast track.

Re: Fast Tracking

Posted: Thu Sep 14, 2017 8:47 am
by nirajsys@gmail.com
Option 3 seems apt.

Option 2 is not recommend as high risk cud be caused through rework in fast tracking.

Option 1 is related to identified risk handling.

Option 4 is related to crashing.

Pls advise.

Re: Fast Tracking

Posted: Mon Sep 18, 2017 9:13 am
by maverick
Fast Tracking essentially relate to having a parallel arrangement to complete a task. To me, option 3 makes sense as using a preferential logic or soft or preferred logic would facilitate fast tracking. Hence #3. Activities have preferential dependencies should be the choice.

Re: Fast Tracking

Posted: Mon Jul 16, 2018 3:16 pm
by ashishmalik479
Please help me with this query:

Out of fast-tracking & Crashing, which technique one should use when network diagram cannot be changed.

For reference this is the exact question:
Q. After completing the schedule network analysis, you find out that your project schedule is taking too long and you also find that you cannot change your network diagram. In such cases, in order to get the project completed faster, what option do you have?

A. Nothing can be done
B. Crash the project
C. Perform resource leveling
D. Fast track the project

Re: Fast Tracking

Posted: Wed Jul 18, 2018 2:33 pm
by manishpn
the question makes little sense to me, unless maybe I am missing something.

If the network diagram cannot be changed , no technique can be useful as resource leveling or compression technique will eventually optimize/change the plan

Re: Fast Tracking

Posted: Tue Jul 24, 2018 5:04 pm
by ashishmalik479
manishpn wrote:the question makes little sense to me, unless maybe I am missing something.

If the network diagram cannot be changed , no technique can be useful as resource leveling or compression technique will eventually optimize/change the plan

Even I thought the same, because if network diagram cannot be changed then you cannot use any of the schedule compression techniques.
But as per the question, option B. Crash the project is the correct answer. Which, I'm unable to understand why?

As per the explanation, it says:
There are two ways to do schedule compression: fast tracking and crashing. As the question clearly says that the network diagram cannot change, fast tracking is not possible, and you can solve the problem only by crashing the project.

So, I'm really wondering how option B is the correct. There is nothing like this stated/mentioned in PMBOOK as well.

Re: Fast Tracking

Posted: Wed Jul 25, 2018 10:04 am
by manishpn
crashing is also done to compress the schedule, so i would not spend more time on such questions

Re: Fast Tracking

Posted: Thu Aug 02, 2018 3:28 pm
by ashishmalik479
manishpn wrote:crashing is also done to compress the schedule, so i would not spend more time on such questions

Sorry, I could not understand your reply.
What if this or this type of question comes in the exam? You have to choose an answer, you cannot just leave it unanswered.

And, if you are choosing crashing, then why not Fast tracking?

Re: Fast Tracking

Posted: Fri Aug 03, 2018 6:37 pm
by manishpn
Questions without a logic does not come in Exam,

look at crashing definition in PMBOK, its a schedule shortening technique,

I would not spend time on such questions which are of not good quality