PMP Exam Tip: The Project Schedule

This forum is for members to share and gain knowledge of Project Management. Got a question about project management? Need help with a problem? Wish to offer tips and advice? Post here.
Post Reply
User avatar
Expert Member
Expert Member
Posts: 103
Joined: Fri 05 Mar 2010 11:19 pm

In project management, a schedule consists of a list of a project's tasks with intended start and finish dates. Tasks are the lowest element in a schedule; they are not further subdivided. Those items are estimated in terms of resource requirements, budget and duration, linked by dependencies and scheduled. Project Scheduling helps identify all of the tasks that are required to complete a project on time. It adds dependencies between tasks so that if one task slips, the tasks related to it slip.

[On a side note: As we mentioned in last weeks tip, in many organizations the terms "project management plan" and "project schedule" are often used interchangeably. If this is the case in your organization, then please make sure that you understand that for the PMP Exam, these are two distinctly different documents. Please refer back to last week's tip for the discussion of the project management plan.]

Before a project schedule can be created, a project manager will typically have a work breakdown structure (WBS), an effort estimate for each task, and a resource list with availability for each resource. If these are not yet available, it may be possible to create something that looks like a schedule, but it will essentially be a work of fiction. They can be created using various estimation methods. A good best practice is to include the people who will perform the actual work in the estimation process. The reason for this is that a schedule itself is an estimate: each date in the schedule is estimated, and if those dates do not have the buy-in of the people who are going to do the work, the schedule will be inaccurate.

In many industries, such as engineering and construction, the development and maintenance of the project schedule is the responsibility of a full time scheduler or team of schedulers, depending on the size of the project. And though the techniques of scheduling are well developed, they are inconsistently applied throughout industry. Standardization and promotion of scheduling best practices are being pursued by the Association for the Advancement of Cost Engineering (AACE), the Project Management Institute (PMI). In some large corporations, scheduling, as well as cost, estimating, and risk management are organized under the department of project controls.

The PMBOK Guide 4th Edtion says the following about the Project Schedule: As a minimum, the project schedule includes a planned start date and planned finish date for each activity. Develop Schedule is the process of analyzing activity sequences. durations, resource requirements, and schedule constraints to create the project schedule.

Read more about Project Schedule in the PMBOK Guide 4th Edtion from 6.5.3 to 6.5.4
Until Next Time,
Cornelius Fichtner, PMP
Expert Member
Expert Member
Posts: 57
Joined: Thu 20 Sep 2012 10:19 am
Location: France

Hi all,

Understanding and implementing a project schedule means not only coming to terms with the start and finish dates of a given task in the WBS, but also being able to understand how to manage and monitor the project schedule in its entirety when contingencies arise.
Quite often contingencies result in certain tasks not being implemented according to the initial schedule, and i believe this is a common occurence in the PM field. However, great emphasis should be placed on the global schedule in order to remain within the constraints of the "Golden triangle".

Another important point to mention here is the relationship between tasks in the hierarchical project decomposition (another term for the WBS). Under the assumption of clearly defined actions and tasks, the types of interdependence that exists between them is relatively well known, but when for example, a specific project deal with a technology innovation project, it would be unrealistic to assume that task and concept definitions are known in advance. They may be roughly defined but should be expected to change during the development phase in the lifecycle model. Therefore, innovation in conjunction with the project schedule represent a journey of discovery where any evolution or progress is assessed in terms of the results obtained rather than in terms of a predefined schedule. Therefore, the schedule is there to reassure relevant stakeholders and provide a reference point from which a project can be managed.

Kindest Regards,
Mohamed Benmerikhi
Post Reply