Scheduling: Critical path, PERT and Gantt

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 5: Line 5:
 
Under the aspect of Complexity in project management, '''Scheduling''' is the development and control of a plan which details when and how the products or services defined in a project scope will be delivered. <ref name=PMI></ref>
 
Under the aspect of Complexity in project management, '''Scheduling''' is the development and control of a plan which details when and how the products or services defined in a project scope will be delivered. <ref name=PMI></ref>
  
The resulting plan is known as a '''project schedule''', which can also be used as a tool for management of stakeholders' expectations, means of communication and/or evaluating performance. Project data like planned dates, activities, resources, constraints, dependencies
+
The resulting plan is known as a '''project schedule''', which can also be used as a tool for management of stakeholders' expectations, means of communication and/or evaluating performance. Project data like planned dates, activities, resources, constraints, dependencies and activity sequence and duration are all inputs to the project schedule, and should be constantly monitored and updated by the project management team. To properly create and use the project schedule with the aforementioned inputs, the team must select the '''scheduling method''' that best suits the needs of their project.
 +
 
 +
'''Critical path method (CPM)''', '''Program evaluation and review technique (PERT)''' and '''Gantt''' are the three scheduling methods that are covered in this article.
 +
 
 +
The focus of this article is to help the reader:
 +
 
 +
* Understand the concept and purpose of each method
 +
* in which cases a particular method excels at so the reader can assess which method fits best their case, th
 +
 
 +
 
  
 
=References=
 
=References=
Line 12: Line 21:
 
<ref name="PMI"> Project Management Institute, Inc. ''Guide to the Project Management Body of Knowledge (PMBOK® Guide)''. 2017. Chapter 6, page 175. Retrieved from  
 
<ref name="PMI"> Project Management Institute, Inc. ''Guide to the Project Management Body of Knowledge (PMBOK® Guide)''. 2017. Chapter 6, page 175. Retrieved from  
 
https://app.knovel.com/hotlink/toc/id:kpGPMBKP02/guide-project-management/guide-project-management
 
https://app.knovel.com/hotlink/toc/id:kpGPMBKP02/guide-project-management/guide-project-management
 +
<ref name="PSfS"> Practice standard for scheduling

Revision as of 17:54, 14 February 2019

Developed by Frank Almirudis, currently under construction

Abstract

Under the aspect of Complexity in project management, Scheduling is the development and control of a plan which details when and how the products or services defined in a project scope will be delivered. [1]

The resulting plan is known as a project schedule, which can also be used as a tool for management of stakeholders' expectations, means of communication and/or evaluating performance. Project data like planned dates, activities, resources, constraints, dependencies and activity sequence and duration are all inputs to the project schedule, and should be constantly monitored and updated by the project management team. To properly create and use the project schedule with the aforementioned inputs, the team must select the scheduling method that best suits the needs of their project.

Critical path method (CPM), Program evaluation and review technique (PERT) and Gantt are the three scheduling methods that are covered in this article.

The focus of this article is to help the reader:

  • Understand the concept and purpose of each method
  • in which cases a particular method excels at so the reader can assess which method fits best their case, th


References

  1. Project Management Institute, Inc. Guide to the Project Management Body of Knowledge (PMBOK® Guide). 2017. Chapter 6, page 175. Retrieved from https://app.knovel.com/hotlink/toc/id:kpGPMBKP02/guide-project-management/guide-project-management

Cite error: <ref> tag with name "PSfS" defined in <references> is not used in prior text.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox