Please login or join to subscribe to this thread
Project Schedule development is an iterative process and recuring activity during the project. The first loop may not consider resource constraints but just apply estimates for activity durations to the network diagram. Then you will see the bare resource requirements. Now resource leveling and applying resource calendars set in, because you need to make the schedule realistic in terms of resource allocation.
So you loop until you get schedule that not only satisfies dependencies between activities but also is feasible and has a good usage of resources.
It may help you to browse the Practice Standards for Scheduling and for Estimating to get a better understanding.
A project manager always has to balance constraints and live with a compromise.
What you are asking is a common mistake in the practice (I am not saying you are doing that) because some project managers forget to update the project calendar and the resource calendar when started planning. Those are a critical input when you estimate activity duration. That´s the place where you are considering both calendars. Resource calendar is something that has to be created and maintained at organizational level.
Hi Thomas. I second your opinion and deeply appreciate the fact that the picture gets developed progressively and ideally speaking there can not be a rigid sequence to it.
However, as a matter of theoretical representation, I do feel that may be adding "Create resource requirement map" would give us a chance to sit and contemplate on the timing of the resources availability. Hence thought what if it was there in the Process Group and Knowledge Area Map.
Thanks for the reply....
Thanks Sergio for your inputs!
the 'resource requirements map' may be seen as a part of the scheduling model, e.g. a resource histogram. Several tools support resource based scheduling, allowing to distribute effort over duration in several ways (front- or end-loaded, equal distribution), and hence optimizing resource usage.
Critical Path Method calculates project schedule ignoring resource constraints. As the result you will get project resource requirements if resources are not limited.
Entering resource availability constraints and leveling your schedule you will get resource requirements that do not exceed their availability.
Resource calendar describes time periods when this specific resource can work, nothing else.
After going through all the above discussions, I feel
1. Resource Calendars are important. Because, since the projects are agile and progressively explored, it is valuable to have information regarding the availability of the resources. This enables PMs to simply pick the available resources and get the job done.
2. What I was suggesting (resource requirement calendar), is not present explicitly in PMBOK process map. However, it is implicitly developed while realizing the project schedule through schedule and resource levelling.
So, this is what is the sequence I infer now:
Estimate activity duration(Ignoring resource calendar)
Create network diagram (tentative schedule estimate by simply adding the time of all these activites)
Apply resource and schedule levelling to create final schedule.
Also, we may never need to create resource requirement calendar because in Agile, the progressive backlog refinement and frequent changes will add huge redundancy in creating such a calendar.
Have I inferred correct? Thanks.
A couple of resources for you:
- PMI's Standard for Portfolio Management
- the following article on PMI's website:
...- Portfolio resource management - the most significant challenge to project management effectiveness
I think you're on the right track, when dealing with shared resources. Individual projects can identify when they will require specific resources, but managing overall resource availability happens outside of the individual project. This is, in part, because when there is an availability conflict between projects regarding when a resource is "required", somebody is either going to have to wait or get a different resource. The individual project manager will need to make the case for getting the resource, but won't be making that decision.
Please login or join to reply