PMP certification training states that the time management knowledge area deals primarily with the relationship of activities, their starting and end times, and project schedule. It also ensures timely fulfillment of each project activity. Time management requires that the project activities be identified, their interrelationships defined, a network diagram created, and the schedule network analysis performed.
Take part in our 100% online & self-paced 1-hour PMP training.
The 6th process in this knowledge area is to Develop Schedule. This process combines the information from previous processes and creates the overall project schedule. This includes the start and ending dates for each activity within a project. We can also state that the Project schedule, as taught in the online PMP course is the final result of the schedule network analysis, and all previous planning processes.
This article will provide a detailed overview of project scheduling techniques, the project scheduling process, as well as examples of project schedules.
What is the Objective?
The project schedule shows when each activity will begin and end, who will do which activity, and which activity is dependent on which activity. After finalizing the project schedule, you can determine the overall project duration.
You can show a project schedule with or without dependencies. Let’s say, for example, that testing of a project activity is dependent on the development of the related activity. This dependency may or not be shown on the project schedule. These relationships in the network diagram can affect and determine the start/end dates for each activity. The project schedule must also show these dates.
3 Common Formats
The project schedule can be represented in three common formats within a project.
Project Schedule Format 1: Network Diagram
Network Diagrams show the interrelationship between activities using arrows. They are created by visualizing project activities in boxes with activity IDs. Network diagrams show when an activity will begin earlier, later, or at the same moment as another activity.
Project Schedule Format #2: Milestone charts
Milestone charts are a way to show the critical dates in a project’s timeline. Milestones are not of any duration and represent an important moment in a project’s history. Milestones don’t usually have an assignee.
This example shows that there are seven milestones for this software project. The project’s start, completion, design, coding, testing, implementation, and completion of the project. There will be many activities in a software project. However, the milestone chart shows only 7 major steps and the dates for each milestone.
Your entry was not saved. Please try again. We have sent you links! You should have already received an email from masterofproject.com. If you have not received an email, please check your spam folders. You can also add masterofproject.com on the safe senders list to continue receiving our emails. Project Schedule Format #3: Bar charts and Gantt charts
Milestone charts look similar to Gantt or bar charts. However, milestone charts only show the most important events in a project. Gantt charts and bar charts show activity ID, activity names, duration, start, and end dates for project activities in a list. As you can see, there are 10 projects activities. Their duration, start and ending dates are listed in this chart.
Gantt charts are poor planning tools. Gantt charts are not activity-specific and do not show the critical path or relationship between activities of a project, as network diagrams do.
Gantt charts can be used to track progress and provide control. To show how many people are using the Gantt chart,