I have seen your post here and I must say that it's perfectly right on what you have said.
Can you please explain me in detail,
Rule 20: Know the Value/Cost of Time on the Project, Is this Value of a Project?
Rule 22: Know the Doubled Resource Estimated Duration (DRED) or the Crash Duration of all CP activities and use them to optimize the schedule, How we will calculate this?
Thanks,
Samba
Member for
18 years 10 months
Member for18 years10 months
Submitted by Nader K. Rad on Sun, 2012-02-26 08:44
Thanks for the comment. I would be happy to know that you’ve downloaded the ebook; donations are not as important as connecting to other professionals and having their feedback. It would also be great if you introduce it to your clients and students.
I thought about the start and finish milestones and finally, decided not to issue it as a rule and just explained it in another related rule.
I’ve used “be careful” instead of “you should”, where rules have some level of tolerance. If you have a better sentence, please let me know; I’m not fluent in English :)
rule 07 is stronger than rule 06 and covers it. I’ve presented them in two different rules just because rule 06 is unavoidable, but rule 07 has a little tolerance. They are also in two different levels of professionalism.
about the splitting, I’m afraid that we are using “splitting” in two different meanings. Are you talking about decomposing the activity into two or more separate activities? What I mean by splitting is to keep having “one” activity, and add a pause and resume period to it (PMI and DoD use the word in the same way).
I tried hard, to limit these rules to abstract rules of planning and did not cover any concrete planning rules or rules directly related to control/maintenance/tracking area. However, I would start collecting and presenting rules for those areas later.
One more: in general, I feel it's good practice to start the schedule with a single milestone or activity (source) and finish it similarly (sink). I'm not sure it rises to the level of a Rule: maybe a guideline?
Fraternally in project management,
Steve the Bajan
Member for
20 years 7 months
Member for20 years7 months
Submitted by Stephen Devaux on Thu, 2012-02-16 16:21
Hi, Nader. Good job, I think! I appreciate the effort, as last week I had been asked by a client to put together a similar checklist! I especially like Rules 04, 05, 10, and 19.
Without downloading the ebook (which I won't do because I don't think I should without making a donation), it's hard to know exactly what you mean by some of these (for example, 01, 02, 03, 12, 13, and 18.): what does "Be Careful with" mean, exactly?
I'd change Rule 06 to: "Each Activity's start Should Have at Least One Predecessor and Each Activity's Finish Should Have at Least One Successor." This would also obviate the need for Rule 07 (Dangling Activities).
I absolutely disagree with Rule 15 -- splitting of activities should never be done unthinkingly, but it can be VERY important to split activities that have an FF or SF predecessor, especially if they also have an SS or SF successor. Not doing this can lead to the Reverse Critical Path Anomaly, and delay the project for no reason other than the software's algorithm. Perhaps you could change Rule 15 to "Do not Split Activities Unthinkingly"?
I would add a couple more rules:
Rule 20: Know the Value/Cost of Time on the Project.
Rule 21: Strongly discourage doing out-of-sequence work. First, the schedule must be changed.
Rule 22: Know the Doubled Resource Estimated Duration (DRED) or the Crash Duration of all CP activities and use them to optimize the schedule.
Rule 23: Know the Critical Path Drag (if you don't know what this is, read this current Defense AT&L article) of all activities, their Drag Costs (see Rule 20) and their True Costs (True Cost = Resource Cost plus Drag Cost).
But overall, I feel you did a very nice job. If you like, I'd be happy to mention your ebook download site to clients and students. (But, like me, they probably won't donate anything!)
Fraternally in project management,
Steve the Bajan
Member for
16 years 9 months
Member for16 years9 months
Submitted by James Williams on Thu, 2012-02-16 16:20
Member for
15 years 4 monthsHi Devaux,I have seen your
Hi Devaux,
I have seen your post here and I must say that it's perfectly right on what you have said.
Can you please explain me in detail,
Rule 20: Know the Value/Cost of Time on the Project, Is this Value of a Project?
Rule 22: Know the Doubled Resource Estimated Duration (DRED) or the Crash Duration of all CP activities and use them to optimize the schedule, How we will calculate this?
Thanks,
Samba
Member for
18 years 10 monthsDear Stephen;Thanks for the
Dear Stephen;
Thanks for the comment. I would be happy to know that you’ve downloaded the ebook; donations are not as important as connecting to other professionals and having their feedback. It would also be great if you introduce it to your clients and students.
Thanks again
Yours
- Nader Khorrami Rad, PMP
Member for
13 years 10 monthsThank You Engr. Nader
Thank You Engr. Nader
Member for
20 years 7 monthsOne more: in general, I feel
One more: in general, I feel it's good practice to start the schedule with a single milestone or activity (source) and finish it similarly (sink). I'm not sure it rises to the level of a Rule: maybe a guideline?
Fraternally in project management,
Steve the Bajan
Member for
20 years 7 monthsHi, Nader. Good job, I
Hi, Nader. Good job, I think! I appreciate the effort, as last week I had been asked by a client to put together a similar checklist! I especially like Rules 04, 05, 10, and 19.
Without downloading the ebook (which I won't do because I don't think I should without making a donation), it's hard to know exactly what you mean by some of these (for example, 01, 02, 03, 12, 13, and 18.): what does "Be Careful with" mean, exactly?
I'd change Rule 06 to: "Each Activity's start Should Have at Least One Predecessor and Each Activity's Finish Should Have at Least One Successor." This would also obviate the need for Rule 07 (Dangling Activities).
I absolutely disagree with Rule 15 -- splitting of activities should never be done unthinkingly, but it can be VERY important to split activities that have an FF or SF predecessor, especially if they also have an SS or SF successor. Not doing this can lead to the Reverse Critical Path Anomaly, and delay the project for no reason other than the software's algorithm. Perhaps you could change Rule 15 to "Do not Split Activities Unthinkingly"?
I would add a couple more rules:
Rule 20: Know the Value/Cost of Time on the Project.
Rule 21: Strongly discourage doing out-of-sequence work. First, the schedule must be changed.
Rule 22: Know the Doubled Resource Estimated Duration (DRED) or the Crash Duration of all CP activities and use them to optimize the schedule.
Rule 23: Know the Critical Path Drag (if you don't know what this is, read this current Defense AT&L article) of all activities, their Drag Costs (see Rule 20) and their True Costs (True Cost = Resource Cost plus Drag Cost).
But overall, I feel you did a very nice job. If you like, I'd be happy to mention your ebook download site to clients and students. (But, like me, they probably won't donate anything!)
Fraternally in project management,
Steve the Bajan
Member for
16 years 9 monthsHi,This is a good starting
Hi,
This is a good starting list, thanks for sharing it.
Regards.