Project Management Central
|
Please login or join to subscribe to this thread
|
|||
|
|||
Suhail Iqbal
Suhail Iqbal PMIATP CIPM FAAPM MPM MQM CLC CPRM SCT AEC SDC SMC SPOC PRINCE2 MCT| PM Training School
Rawalpindi, Punjab, Pakistan
When the team is acquired and human resource is actually mobilized, that is the time when we exactly know the actual time commitment of that human resource. Earlier in planning, we do use a resource calendar which is not exact and is used as rolling wave plan. It is the best guess of a certain human resources' time availability, on which we plan everything. But as soon as the actual resource is onboard and it's time commitment is known, we can go back to planning and make necessary amendments wherever necessary.
In planning you define when you need a particular resource (either manpower or material). You prepare your project plan but you need to revise your schedule in accordance with their availability.This is the time when resource calendar helps.You must identify the resource availability,delivery time and their need in critical path before finalizing your schedule.
Planning is an iterative process and in the initial stages you plan on a high level and once things are clear you revisit the planning and plan it in low level and it is overlapping other processes .
that is the reason output of execution process becomes input of planning process. 
Sergio Luis Conte
Helping to create solutions for everyone| Worldwide based Organizations
Buenos Aires, Argentina
Please let me say that you are making a mistake (and sorry if I did not understand): there is no time defined in the PMBOK and there is no precedence defined because the PMBOK does not define a project life cycle. Second, resource calendar is for any type of resource, not for human resource only. About human beings, when you plan, you have no names, you only have roles assigned to activities. When you adquire the project team those roles become names. If you ask me, I try to put names when I am planning but it is not easy.
...
1 reply by Ahmed Karar
Jan 24, 2016 1:05 PM
Ahmed Karar
...
It is really great to have a discussion in this topic, and I am grateful for you trying to let me grasp this matter. Well, Mr. Sergio Luis Con, thank you for your help by commenting on inquire of mine and I tend to agree with you to some extent. Let me confirm a thing I agree with you and then explain where is the confusing part of the matter.
First, I agree that Resource Calendar is relevant to any type of resources such as people, material or equipment ...etc. Also I am firmly convinced that PMBOK does not introduce a project life cycle which is relevant to specific application area, and all of us should make the best of use of the PMBOK's management processes to tailor what suit the project we are working on. Second, I am explaining where I could not be agreeing with you. while it is right there is no explicit mention of precedence, there is logical precedence should be taken into account such as Estimate activity resources should be before Acquire project team so if there is a project document as input to the first one and it is created in the second one which is followed, so this is what sometime causes confusion especially in written sources where there is no a way for interactive communication. Moreover, in PMBOK the way some of project documents have been introduced as inputs/outputs are not clear enough. For example let me take the Resource calendar has be defined in Estimate activity resources as input , however, in Acquire project team as output with different definition but with the same subtitle Resource calendar, and for me is a kind of confusion induce. My suggestion for such a problem to distinguish between them is to define the first one as Preliminary Resource Calendar where a project manager finds the potential availability and the second one could be Confirmed/Finalized Resource Calendar where the project manager finds the all availability of the project. Therefore when the project manager reaches this Confirmed/Finalized Resource Calendar, it implies he/she has the first Resource Availability of the first iteration for issues influence it, which will the preliminary one for the next iteration if there is a change takes place. I believe that in this way the confusion will be resolved. 
Ahmed Karar
Project Engineer| Ministry of Water Resources, Irrigation and Electricity
Khatoum, Khatoum/ Jabl Awlia, Sudan
Jan 22, 2016 7:14 AM
Replying to Sergio Luis Conte
...
Please let me say that you are making a mistake (and sorry if I did not understand): there is no time defined in the PMBOK and there is no precedence defined because the PMBOK does not define a project life cycle. Second, resource calendar is for any type of resource, not for human resource only. About human beings, when you plan, you have no names, you only have roles assigned to activities. When you adquire the project team those roles become names. If you ask me, I try to put names when I am planning but it is not easy.
First, I agree that Resource Calendar is relevant to any type of resources such as people, material or equipment ...etc. Also I am firmly convinced that PMBOK does not introduce a project life cycle which is relevant to specific application area, and all of us should make the best of use of the PMBOK's management processes to tailor what suit the project we are working on. Second, I am explaining where I could not be agreeing with you. while it is right there is no explicit mention of precedence, there is logical precedence should be taken into account such as Estimate activity resources should be before Acquire project team so if there is a project document as input to the first one and it is created in the second one which is followed, so this is what sometime causes confusion especially in written sources where there is no a way for interactive communication. Moreover, in PMBOK the way some of project documents have been introduced as inputs/outputs are not clear enough. For example let me take the Resource calendar has be defined in Estimate activity resources as input , however, in Acquire project team as output with different definition but with the same subtitle Resource calendar, and for me is a kind of confusion induce. My suggestion for such a problem to distinguish between them is to define the first one as Preliminary Resource Calendar where a project manager finds the potential availability and the second one could be Confirmed/Finalized Resource Calendar where the project manager finds the all availability of the project. Therefore when the project manager reaches this Confirmed/Finalized Resource Calendar, it implies he/she has the first Resource Availability of the first iteration for issues influence it, which will the preliminary one for the next iteration if there is a change takes place. I believe that in this way the confusion will be resolved. |
|||
Please login or join to reply
ADVERTISEMENTS
|
Information is not knowledge, - Frank Zappa |
