Hans-Georg BessHead of project management| eos.Uptrade GmbHHamburg, Germany
In my opinion reducing scope is not really a compression of the schedule. If you reduce scope, this has the effect of shortening your schedule. Compressing and shorting are two different things for me.
Compression is doing the same amount of work in shorter time by fast tracking or crashing. Shortening scope shortens schedule automatically because you have less work to do but the schedule is not really compressed.
...
1 reply by Rami Kaibni
Jan 23, 2016 2:32 PM
Rami Kaibni
...
Thanks for your input Hans. I do not disagree with you but Rita Mulcahy's book mentions otherwise. If you have access to the 8th edition updated, please check page 232.
Reducing scope as a technique to reduce time or recover delayed schedule is real not a good practice since you maybe affecting the project deliverable and what sponsor is expecting with the project itself. Better be more creative and try other alternatives depending on the project characteristic and team capabilities. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jan 23, 2016 2:00 AM
Replying to Prasanna Arkadi
...
Answer is NO. However for any project; the Scope statement is finalized with final list of requirements. However, there are some requirements which are must to make the project successful and others are like good to have type. Hence, we can make the ABC analysis of requirements and must complete the deliverable on/before the schedule timeline. The love to have type deliverables can be delivered with some extra time if required. I mean to say there are some operational requirements and some are aesthetic requirements.
Prasanna, Can you elaborate more on your answer as I am not sure I understood you clearly. Thanks. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jan 23, 2016 2:16 AM
Replying to PANKAJ KUMAR JOSHI
...
In my opinion as per PMBOK fast tracking and scope reduction are two different things.
In practical side, scope reduction should not be used as a tool to compress the schedule. It will raise a lot of questions.
In general, scope reduction can happen when we identify some activity which is not required now due to technical or practical reasons. But it should be identified in scope planning stage.
Also another possibility is when sponsor/customer allows to reduce the scope of work for early execution .
Pankaj, I agree there are two different things but what confused me is that in Rita's Book, it gives scope reduction as an option .... Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jan 23, 2016 2:19 AM
Replying to Suhail Iqbal
...
When you try to fast-track sometimes you have to come up with a creative solution which seems otherwise not possible. To make it possible, you might have to pay some cost and resultantly may slightly smoothen up the specific requirement in scope. But this is only in extreme cases where you are stretched to the limit and still more fast-tracking is required. This is the last resort after which crashing will have to be done.
Suhail, usually it is better to explore all options for Fast Tracking before we jump into Crashing right ? Can you explain to me why please.
As per my understanding:
Fast Tracking might result in rework and increased risk.
Crashing might result in increased risk and cost.
Both has disadvantages so what make Fast Tracking better than Crashing in your opinion ?
...
1 reply by Suhail Iqbal
Jan 23, 2016 5:11 PM
Suhail Iqbal
...
Definitions are right but in order of priority, if I want to intelligently compress schedule with sufficient thought process is fast-tracking. When I have no time to think, emergency lurking over my head, I will have to resort to extreme measures, life life-saving measures. At that point I will not bother if it is convenient, but only if it can save my project. Therefore crashing is for extreme measures and Fast-Tracking is carefully thought out measures.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jan 23, 2016 5:19 AM
Replying to Hans-Georg Bess
...
In my opinion reducing scope is not really a compression of the schedule. If you reduce scope, this has the effect of shortening your schedule. Compressing and shorting are two different things for me.
Compression is doing the same amount of work in shorter time by fast tracking or crashing. Shortening scope shortens schedule automatically because you have less work to do but the schedule is not really compressed.
Thanks for your input Hans. I do not disagree with you but Rita Mulcahy's book mentions otherwise. If you have access to the 8th edition updated, please check page 232.
...
1 reply by Hans-Georg Bess
Jan 23, 2016 3:42 PM
Hans-Georg Bess
...
Thanks Rami, I know the definition of Rita, I used this book als many others did for PMP prep.
I had a look on page 232 but unfortunately I do not have the same version. I have the 8th edition without updates. But I found an excercise:
What is the impact of the schedule-shortening options listed?
One option is fast-tracking, another one is scope reduction, the others are crashing and cut quality.
So I don't get your point, I see scope reduction as one option, fast tracking as another. This is how I understood it. Even the PMBok mentions two compression techniques, again fast tracking and crashing.
It is just a wording, for PMP exam go with the definitions of PMBoK and Rita and in real projects you know what to do because you are a good PM!
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Gentlemen,
Rita's Book (8th Edition Updated) - Page 232 mentions scope reduction as an option to Fast Track Schedule but the last resort to be used and it has advantages (Save cot, resources and time) and disadvantages (Negatively Impact Customer Satisfaction).
Can you advise on this please. Saving Changes...
Hans-Georg BessHead of project management| eos.Uptrade GmbHHamburg, Germany
Jan 23, 2016 2:32 PM
Replying to Rami Kaibni
...
Thanks for your input Hans. I do not disagree with you but Rita Mulcahy's book mentions otherwise. If you have access to the 8th edition updated, please check page 232.
Thanks Rami, I know the definition of Rita, I used this book als many others did for PMP prep.
I had a look on page 232 but unfortunately I do not have the same version. I have the 8th edition without updates. But I found an excercise:
What is the impact of the schedule-shortening options listed?
One option is fast-tracking, another one is scope reduction, the others are crashing and cut quality.
So I don't get your point, I see scope reduction as one option, fast tracking as another. This is how I understood it. Even the PMBok mentions two compression techniques, again fast tracking and crashing.
It is just a wording, for PMP exam go with the definitions of PMBoK and Rita and in real projects you know what to do because you are a good PM!
...
1 reply by Rami Kaibni
Jan 23, 2016 4:14 PM
Rami Kaibni
...
In the real world, I have no isses Hans - I am talking from the exam perspective.
It is good that you agree that this was mentioned as a schedule compression technique in Rita's book. Now, that being said, and in order for you to have a better understanding of my concern, here is it:
One exam question asked what is NOT a schedule compression technique and the right answer was:
Reduction of Scope
This answer contradicts what is written in Rita's book so that was the reason that triggered the question.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jan 23, 2016 3:42 PM
Replying to Hans-Georg Bess
...
Thanks Rami, I know the definition of Rita, I used this book als many others did for PMP prep.
I had a look on page 232 but unfortunately I do not have the same version. I have the 8th edition without updates. But I found an excercise:
What is the impact of the schedule-shortening options listed?
One option is fast-tracking, another one is scope reduction, the others are crashing and cut quality.
So I don't get your point, I see scope reduction as one option, fast tracking as another. This is how I understood it. Even the PMBok mentions two compression techniques, again fast tracking and crashing.
It is just a wording, for PMP exam go with the definitions of PMBoK and Rita and in real projects you know what to do because you are a good PM!
In the real world, I have no isses Hans - I am talking from the exam perspective.
It is good that you agree that this was mentioned as a schedule compression technique in Rita's book. Now, that being said, and in order for you to have a better understanding of my concern, here is it:
One exam question asked what is NOT a schedule compression technique and the right answer was:
Reduction of Scope
This answer contradicts what is written in Rita's book so that was the reason that triggered the question. Saving Changes...
Suhail, usually it is better to explore all options for Fast Tracking before we jump into Crashing right ? Can you explain to me why please.
As per my understanding:
Fast Tracking might result in rework and increased risk.
Crashing might result in increased risk and cost.
Both has disadvantages so what make Fast Tracking better than Crashing in your opinion ?
Definitions are right but in order of priority, if I want to intelligently compress schedule with sufficient thought process is fast-tracking. When I have no time to think, emergency lurking over my head, I will have to resort to extreme measures, life life-saving measures. At that point I will not bother if it is convenient, but only if it can save my project. Therefore crashing is for extreme measures and Fast-Tracking is carefully thought out measures.
Community Champion
