Program evaluation and review technique (PERT) - Revision history

Tkokotas at 15:29, 18 December 2018

2018-12-18T15:29:30Z

← Older revision		Revision as of 15:29, 18 December 2018
Line 1:		Line 1:
	~~[[ Category:Project Management \| Program evaluation and review technique ]]~~		''Developed by Thomas Kalmus''
	~~[[ Category:Product Development \| Program evaluation and review technique ]]~~

	The Program Evaluation and Review Technique (PERT) is a method used in project management for planning, scheduling and coordinating the tasks of a project. It is based on a network diagram analysis of the different tasks that are involved. PERT is specifically suited for large, complex and nonrepititive projects. The aim of this article is to give an overview of this method with examples of applications and a comparison to other existing network based project management tools. It will also explore the usage of this method in todays projects, its advantages and limitations.		The Program Evaluation and Review Technique (PERT) is a method used in project management for planning, scheduling and coordinating the tasks of a project. It is based on a network diagram analysis of the different tasks that are involved. PERT is specifically suited for large, complex and nonrepititive projects. The aim of this article is to give an overview of this method with examples of applications and a comparison to other existing network based project management tools. It will also explore the usage of this method in todays projects, its advantages and limitations.
Line 153:		Line 153:
	# ''The project schedule management model based on the program evaluation and review technique and Bayesian networks'', Zhao, Zhigang; Jin, Yong, 2011. Presents the usage of Bayesian networks to determine the probability of the time of a certain activity.		# ''The project schedule management model based on the program evaluation and review technique and Bayesian networks'', Zhao, Zhigang; Jin, Yong, 2011. Presents the usage of Bayesian networks to determine the probability of the time of a certain activity.
	# ''RPERT: Repetitive-projects evaluation and review technique'', Aziz, Remon Fayek, 2014. Presents a modified version of PERT, and a sample software implementation that enables the usage of this method. The software takes care of the calculations of the times.		# ''RPERT: Repetitive-projects evaluation and review technique'', Aziz, Remon Fayek, 2014. Presents a modified version of PERT, and a sample software implementation that enables the usage of this method. The software takes care of the calculations of the times.

			[[ Category:Project Management \| Program evaluation and review technique ]]
			[[ Category:Product Development \| Program evaluation and review technique ]]

S141938: /* Bibliography */

2015-09-28T18:39:11Z

Bibliography

← Older revision		Revision as of 18:39, 28 September 2015
Line 152:		Line 152:
	# ''Program evaluation and review techniques II (PERT II)'', Yakhchali, Siamak Haji, 2011, Discussion about the PERT II methodology, which introduces a stochastic approach to determine the time of an activity		# ''Program evaluation and review techniques II (PERT II)'', Yakhchali, Siamak Haji, 2011, Discussion about the PERT II methodology, which introduces a stochastic approach to determine the time of an activity
	# ''The project schedule management model based on the program evaluation and review technique and Bayesian networks'', Zhao, Zhigang; Jin, Yong, 2011. Presents the usage of Bayesian networks to determine the probability of the time of a certain activity.		# ''The project schedule management model based on the program evaluation and review technique and Bayesian networks'', Zhao, Zhigang; Jin, Yong, 2011. Presents the usage of Bayesian networks to determine the probability of the time of a certain activity.
	# ''RPERT: Repetitive-projects evaluation and review technique'', Aziz, Remon Fayek, 2014. Presents a modified version of PERT, and a sample software implementation that enables the usage of this method. The software takes care of the calculations of the times ~~also~~.		# ''RPERT: Repetitive-projects evaluation and review technique'', Aziz, Remon Fayek, 2014. Presents a modified version of PERT, and a sample software implementation that enables the usage of this method. The software takes care of the calculations of the times.

S141938: /* Bibliography */

2015-09-28T18:09:12Z

Bibliography

← Older revision		Revision as of 18:09, 28 September 2015
Line 150:		Line 150:
	# ''Project Management Demystified: Today's Tools and Techniques'', Geoff Reis, provides real life anecodtes about the method, discusses how it became famous and why it is less used now.		# ''Project Management Demystified: Today's Tools and Techniques'', Geoff Reis, provides real life anecodtes about the method, discusses how it became famous and why it is less used now.
	# https://www.mindtools.com/critpath.html, comparison of the PERT method and CPA		# https://www.mindtools.com/critpath.html, comparison of the PERT method and CPA
			# ''Program evaluation and review techniques II (PERT II)'', Yakhchali, Siamak Haji, 2011, Discussion about the PERT II methodology, which introduces a stochastic approach to determine the time of an activity
			# ''The project schedule management model based on the program evaluation and review technique and Bayesian networks'', Zhao, Zhigang; Jin, Yong, 2011. Presents the usage of Bayesian networks to determine the probability of the time of a certain activity.
			# ''RPERT: Repetitive-projects evaluation and review technique'', Aziz, Remon Fayek, 2014. Presents a modified version of PERT, and a sample software implementation that enables the usage of this method. The software takes care of the calculations of the times also.

S141938: /* Bibliography */

2015-09-28T17:58:57Z

Bibliography

← Older revision		Revision as of 17:58, 28 September 2015
Line 143:		Line 143:
	== Bibliography ==		== Bibliography ==

	* ESSENTIALS OF MANAGEMENT, Andrew DuBrin, Section "Program Evaluation and Review Technique", General overview and presentation of the method with all of the steps.		# ''ESSENTIALS OF MANAGEMENT'', Andrew DuBrin, Section "Program Evaluation and Review Technique", General overview and presentation of the method with all of the steps.
	* Programming and Scheduling Techniques, Thomas Uher,Adam S. Zantis, Chapter 13, presentation of the method with an emphasis on the event side compared to the critical path method.		# ''Programming and Scheduling Techniques'', Thomas Uher,Adam S. Zantis, Chapter 13, presentation of the method with an emphasis on the event side compared to the critical path method.
	* The Handbook of Project Management: A Practical Guide to Effective Policies, Trevor L. Young, presentation of the method from a visual side (box drawing and step by step filling)		# ''The Handbook of Project Management: A Practical Guide to Effective Policies'', Trevor L. Young, presentation of the method from a visual side (box drawing and step by step filling)
	* Entrepreneurship Development, S. Anil Kuma, presentation of the method with a discussion of the advantages and disadvantages.		# ''Entrepreneurship Development'', S. Anil Kuma, presentation of the method with a discussion of the advantages and disadvantages.
	* https://www.mindtools.com/critpath.html, comparison of the Critical Path Analysis and PERT, how they differ and how are they connected.		# https://www.mindtools.com/critpath.html, comparison of the Critical Path Analysis and PERT, how they differ and how are they connected.
	* Project Management Demystified: Today's Tools and Techniques, Geoff Reis, provides real life anecodtes about the method, discusses how it became famous and why it is less used now.		# ''Project Management Demystified: Today's Tools and Techniques'', Geoff Reis, provides real life anecodtes about the method, discusses how it became famous and why it is less used now.
			# https://www.mindtools.com/critpath.html, comparison of the PERT method and CPA

S141938: /* See also */

2015-09-28T17:31:44Z

S141938 at 17:30, 28 September 2015

2015-09-28T17:30:40Z

← Older revision		Revision as of 17:30, 28 September 2015
Line 133:		Line 133:
	== See also ==		== See also ==

	[[ Responsibility Assignment Matrix (RACI Matrix) ~~\| Responsibility Assignment Matrix~~ (~~RAM~~) ]]		* [[ Responsibility Assignment Matrix (RACI Matrix) ]]
			* [[ Scheduling techniques in Project Management ]]
			* [[ Critical chain project management (CCPM) ]]
			* [[ Critical Path Method in Construction Industry ]]
			* [[ Critical Chain Project Management ]]

	== Bibliography ==		== Bibliography ==

S141938 at 16:59, 28 September 2015

2015-09-28T16:59:05Z

← Older revision		Revision as of 16:59, 28 September 2015
Line 107:		Line 107:
	PERT is a tool that can be useful in big and complex projects like in the construction industry. As mentioned in the introduction, it was created during the Polaris missile project and had a huge popularity afterwards. But soon, project managers and companies have found that it is too ineffective and error-prone to use it, causing lots of failures. The main reason behind it was the lack of IT tools, which had not the same abilities as now. Another major point was the update step in this method, which requires to reorganize the whole plan and in the case of large projects, this can be a time consuming and confusing step.		PERT is a tool that can be useful in big and complex projects like in the construction industry. As mentioned in the introduction, it was created during the Polaris missile project and had a huge popularity afterwards. But soon, project managers and companies have found that it is too ineffective and error-prone to use it, causing lots of failures. The main reason behind it was the lack of IT tools, which had not the same abilities as now. Another major point was the update step in this method, which requires to reorganize the whole plan and in the case of large projects, this can be a time consuming and confusing step.

	Nowadays the software and hardware part is not a problem anymore. Many management software include PERT charts as part of their functionalities like Microsoft Project (see figure 3) or Oracle Primavera. PERT charts are used to visualize the dependencies between different activities. To see the timing and progress of the project another similar tool is widely used, the Gantt charts. More popular than PERT are the Critical Path diagrams, in which nodes represent the activities, a more readable representation.		Nowadays the software and hardware part is not a problem anymore. Many management software include PERT charts as part of their functionalities like Microsoft Project (see figure 3) or Oracle Primavera. PERT charts are used to visualize the dependencies between different activities. To see the timing and progress of the project another similar tool is widely used, the [[ The Gantt chart and the usage nowadays \| Gantt charts ]]. More popular than PERT are the Critical Path diagrams, in which nodes represent the activities, a more readable representation.

	== Comparison to other tools ==		== Comparison to other tools ==
Line 113:		Line 113:
	[[File:Gantt chart example.png \| thumb \| right \| 300px \| '''Figure 4''': Gantt chart example ]]		[[File:Gantt chart example.png \| thumb \| right \| 300px \| '''Figure 4''': Gantt chart example ]]

	As mentioned, PERT belongs to the family of tools based on network analysis. This category includes also other tools like the Critical Path Analysis, the matrix-based Design Structure Matrix, petri nets. How do they differ from eachother?		As mentioned, PERT belongs to the family of tools based on network analysis. This category includes also other tools like the [[ The Critical Path Method (CPM) \| Critical Path Analysis ]], the matrix-based Design Structure Matrix, petri nets. How do they differ from eachother?

	PERT and Critical Path Analysis are highly related, since one of the steps in PERT is to find the critical path of the project. They differ mainly on the way the timing is estimated and the visualization. In the Critical Path Analysis the activities are represented as nodes, whereas PERT uses nodes to represent events.		PERT and Critical Path Analysis are highly related, since one of the steps in PERT is to find the critical path of the project. They differ mainly on the way the timing is estimated and the visualization. In the Critical Path Analysis the activities are represented as nodes, whereas PERT uses nodes to represent events.
Line 119:		Line 119:
	Gantt charts are used to display the timing of activities and progress of the project (see figure 4). Timings in Gantt charts can be estimated in the same way as in PERT and the whole process of building Gantt charts is almost identical to PERTs process. The use case is the only difference; because Gantt charts have a simplier structure and a better visualization, their usage is much wider and they appear more often in software tools.		Gantt charts are used to display the timing of activities and progress of the project (see figure 4). Timings in Gantt charts can be estimated in the same way as in PERT and the whole process of building Gantt charts is almost identical to PERTs process. The use case is the only difference; because Gantt charts have a simplier structure and a better visualization, their usage is much wider and they appear more often in software tools.

	Design Structure Matrix (DSM) is a modeling technique based on network analysis that can be used for the design, development and management of complex systems. The essential difference between a PERT chart and DSM is the visualization. DSM matrices represent basically the same information as a PERT network, which is different activities and their connections. The advantage of this representation is its conciseness compared to PERT, where lots of space is required to have a readable network (see figure 5). However it doesn't give any information concerning timings of activities. It is less focused on the planning but more on the management.		'''Design Structure Matrix''' (DSM) is a modeling technique based on network analysis that can be used for the design, development and management of complex systems. The essential difference between a PERT chart and DSM is the visualization. DSM matrices represent basically the same information as a PERT network, which is different activities and their connections. The advantage of this representation is its conciseness compared to PERT, where lots of space is required to have a readable network (see figure 5). However it doesn't give any information concerning timings of activities. It is less focused on the planning but more on the management.

	[[File:DSM Tutorial BasicDSM.jpg \| thumb \| right \| 300px \| '''Figure 5''': DSM equivalent of a PERT network ]]		[[File:DSM Tutorial BasicDSM.jpg \| thumb \| right \| 300px \| '''Figure 5''': DSM equivalent of a PERT network ]]
Line 130:		Line 130:
	* PERTBN (Bayesian network) - usage of bayesian networks to determine the duration of the activities.		* PERTBN (Bayesian network) - usage of bayesian networks to determine the duration of the activities.
	* RPERT (repetetive PERT) - usage of PERT in repetitive projects.		* RPERT (repetetive PERT) - usage of PERT in repetitive projects.

			== See also ==

			[[ Responsibility Assignment Matrix (RACI Matrix) \| Responsibility Assignment Matrix (RAM) ]]

	== Bibliography ==		== Bibliography ==

S141938: /* Comparison to other tools */

2015-09-28T16:41:29Z

Comparison to other tools

← Older revision		Revision as of 16:41, 28 September 2015
Line 117:		Line 117:
	PERT and Critical Path Analysis are highly related, since one of the steps in PERT is to find the critical path of the project. They differ mainly on the way the timing is estimated and the visualization. In the Critical Path Analysis the activities are represented as nodes, whereas PERT uses nodes to represent events.		PERT and Critical Path Analysis are highly related, since one of the steps in PERT is to find the critical path of the project. They differ mainly on the way the timing is estimated and the visualization. In the Critical Path Analysis the activities are represented as nodes, whereas PERT uses nodes to represent events.

	Gantt ~~charts are used to display the timing of activities aGantt~~ charts are used to display the timing of activities and progress of the project (see figure 4). Timings in Gantt charts can be estimated in the same way as in PERT and the whole process of building Gantt charts is almost identical to PERTs process. The use case is the only difference; because Gantt charts have a simplier structure and a better visualization, their usage is much wider and they appear more often in software tools.		Gantt charts are used to display the timing of activities and progress of the project (see figure 4). Timings in Gantt charts can be estimated in the same way as in PERT and the whole process of building Gantt charts is almost identical to PERTs process. The use case is the only difference; because Gantt charts have a simplier structure and a better visualization, their usage is much wider and they appear more often in software tools.

	Design Structure Matrix (DSM) is a modeling technique based on network analysis that can be used for the design, development and management of complex systems. The essential difference between a PERT chart and DSM is the visualization. DSM matrices represent basically the same information as a PERT network, which is different activities and their connections. The advantage of this representation is its conciseness compared to PERT, where lots of space is required to have a readable network (see figure 5). However it doesn't give any information concerning timings of activities. It is less focused on the planning but more on the management.		Design Structure Matrix (DSM) is a modeling technique based on network analysis that can be used for the design, development and management of complex systems. The essential difference between a PERT chart and DSM is the visualization. DSM matrices represent basically the same information as a PERT network, which is different activities and their connections. The advantage of this representation is its conciseness compared to PERT, where lots of space is required to have a readable network (see figure 5). However it doesn't give any information concerning timings of activities. It is less focused on the planning but more on the management.

S141938: /* Critical path estimation */

2015-09-28T16:34:58Z

Critical path estimation

← Older revision		Revision as of 16:34, 28 September 2015
Line 63:		Line 63:
	=== Critical path estimation ===		=== Critical path estimation ===

	Once all the time information has been gathered about the different activities, it is possible to estimate the total duration of the project and the starting and ending dates. Determining the critical path comes down to identifying the path that takes the most time. A project cannot be completed as long as ~~his~~ longest component isn't finished. Here are the steps to find this path :		Once all the time information has been gathered about the different activities, it is possible to estimate the total duration of the project and the starting and ending dates. Determining the critical path comes down to identifying the path that takes the most time. A project cannot be completed as long as its longest component isn't finished. Here are the steps to find this path :
	* Step 1 : Starting from the first activity, write the starting and ending times, by adding the duration to the ending time of the preceding activity.		* Step 1 : Starting from the first activity, write the starting and ending times, by adding the duration to the ending time of the preceding activity.
	* Step 2 : Make the same thing but from the end and substract the times instead of adding.		* Step 2 : Make the same thing but from the end and substract the times instead of adding.

S141938: /* Estimation of the time */

2015-09-28T16:34:16Z

Estimation of the time

← Older revision		Revision as of 16:34, 28 September 2015
Line 47:		Line 47:
	=== Estimation of the time ===		=== Estimation of the time ===

	In this step ~~we estimate~~ the amount of time that can be taken by each activity. This time can be determined using a probabilistic or a deterministic approach. Three times need to be defined :		In this step, the amount of time that can be taken by each activity is estimated. This time can be determined using a probabilistic or a deterministic approach. Three times need to be defined :
	* the optimistic time (short time)		* the optimistic time (short time)
	* the pessimistic time (shortest time)		* the pessimistic time (shortest time)

← Older revision		Revision as of 17:31, 28 September 2015
Line 138:		Line 138:
	* [[ Critical Path Method in Construction Industry ]]		* [[ Critical Path Method in Construction Industry ]]
	* [[ Critical Chain Project Management ]]		* [[ Critical Chain Project Management ]]
			* [[ Metra Potential Method ]]
			* [[ The Critical Path Method (CPM) ]]

	== Bibliography ==		== Bibliography ==