Shahul

Procurement is a big issue you can never overlook. Just don’t overdo it as Vladimir wisely suggested when he mentioned that this does not need to be applied to readily available materials, this to keep you focused on the relevant items.

My excuses for moving a little away from the theme.

I just read at another thread a very good comment on your part, seems like debating with you will also be a good learning exercise.

Best regards,
Rafael

Vladimir my reference to by mail means by e-mail is just a way to express it in a sarcastic way.

Talk to you tomorrow the wine and food are ready. Lan for today, for sept 23, a special occasion an anniversary, will have the Muga as I have a taste for Spanish wines.

Don’t worry for Christmas Mike will send us all a bottle of Blue Label King George V, for a few it will be The Macallan Fine and Rare Collection, 1926, 60 Years Old.

Best regards,
Rafael

I don’t know what do you mean by by mail certification.
Today it is computer based multiple-choice exam that checks your knowledge of standard terms and techniques. And you may be sure that you can speak the same language with the person who passed this exam.
But don’t make a mistake thinking that this certification means anything else.

By the way when I passed this exam it was paper and pencil and was suggested at the same dates everywhere in the world. If I remember correctly once in a quarter.

Best Regards,
Vladimir

Samer is right - Max Wideman did very good job.
But PMBOK not only defines but also explains terms.
We need some standard and though I agree that PMBOK Guide is not perfect it is better to have some standard than none at all.

Usually we use multiple WBS for one project, PMBOK Guide defines only one. And I know which one of many that we use people mean when talk about WBS because it was described in PMBOK Guide. I am sure that our approach to project work structuring is superior but I am glad that can easily understand others that use different tools and live in different cultures. Thanks to PMBOK Guide.

Best Regards,
Vladimir

Thanks Samer

I included it into My Favorites for further reading and reference.

This is the kind of glossary I would adopt in CPM specifications by reference or as an introduction to the terms. I like the idea.

You have always been a good source and good to debate with.

Best regards,
Rafael

Vladimir,

A glossary that accepts whatever you want to put into it. Microsoft Glossary is quite different to Primavera and everyone else and PMI very conveniently embraces both, although I believe it is a glossary biased in favor of Primavera as some of its definitions use terms like Fragnets, functionality you only find in nearly extinct P3.

Sorry I prefer Webster as a glossary or dictionary. For a Summary on theory definitely Monarch or Cliff notes would be better.

I agree we need a standard as this is getting into chaos. Yesterday I learned a new definition for Slack, different from old definitions and new Microsoft’s, also different and who knows.

Best regards,
Rafael

Samer

No hard feelings, it is just I have my reserves about PMI.

Regarding the hours requirement you might have 100,000 doing the same irrelevant thing, this equals 1 single hour of irrelevant experience.

I dont believe in mail order certifications.

Best regards,
Rafael

Samer

Regarding PMI keep them as a Christmas present, seems like non-project managers playing project managers. I wonder if they ever managed relevant at risk jobs with their ba…s in the basket. I got not much appreciation for not at risk Project Managers who play in a very convenient way with the money of others. I suspect they were never at the level of true Project Managers, those who really take the risk with their own money.

If this is what PMI Booooo-Book on Body of knowledge is all about then BS.

Sorry for my comments but I don’t see the practical experience required of a true Project Manager in these books and this got to be questioned.

Best regards,
Rafael

Don,t forget to include an activity for submittal review, at times if review process is delayed by the designer this is an issue that might generate EOTs.

It is convenient to place in your Baseline Submittal a time for submittal review, once accepted this has contractual relevance.

Always try to schedule leaving some float for a resubmittal cycle not to be included as part of the original submittal review duration, just a buffer into your float as to avoid submittals becoming critical if you are required to resubmit.

Use of expected finish constraint might be handy to update deliveries, especially when spanning multiple update periods.

It is common practice to issue POs subject to the approval by the Designer. Then after approval manufacturing will proceed unless you write a waiver to the supplier assuming all risk. If the submittal is rejected then under the terms of the PO you can cancel it with no penalty.

I would recommend to create the single WBS phase for placing order, manufacturing and delivery. Usually one person is responsible for all these activities and as the result for the timely delivery of the product.
WBS items usually define some result, and activities under these items reflect the actions necessary to achieve the result.
Your result is delivered generator. To achieve this result it is necessary to place order, to create, and to deliver.
Best Regards,
Vladimir

If the procurement item shall be manufactured then its delivery shall be considered as the subproject. You are right including these subprojects in your schedule.
Materials that are always available don’t require this approach.
Best Regards,
Vladimir