Resource allocation and crashing: Difference between revisions

From DTU ProjectLab
Jump to navigation Jump to search
Wolters (talk | contribs)
Created page with "Abstract pending"
 
Wolters (talk | contribs)
No edit summary
Line 1: Line 1:
Abstract pending
Chapters
 
Abstract
 
Common to all projects is the need to allocate available resources in the best possible manner.
If done correctly by the project manager, she can avoid delays, penalty fees and using unnecessarily many resources. In addition, by analyzing the possibility of crashing the project, the project manager might be able to find a more optimal solution than would be possible by the simple PERT/CPM analysis. Thus this analysis is building upon a PERT/CPM analysis.
 
 
Resource loading
Resource leveling using ALAP heuristic
Resource scheduling
Cost-time trade off
Crashing
Advantages and disadvantages
Crash example

Revision as of 14:48, 11 February 2019

Chapters

Abstract

Common to all projects is the need to allocate available resources in the best possible manner. If done correctly by the project manager, she can avoid delays, penalty fees and using unnecessarily many resources. In addition, by analyzing the possibility of crashing the project, the project manager might be able to find a more optimal solution than would be possible by the simple PERT/CPM analysis. Thus this analysis is building upon a PERT/CPM analysis.


Resource loading Resource leveling using ALAP heuristic Resource scheduling Cost-time trade off Crashing Advantages and disadvantages Crash example