Resource allocation and crashing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
= Crashing a project = | = Crashing a project = | ||
== Cost-time trade off == | == Cost-time trade off == | ||
== Advantages and disadvantages == | |||
= Conclusion = | = Conclusion = | ||
= Annotated bibliography = | = Annotated bibliography = | ||
Revision as of 12:10, 17 February 2019
Contents
Introduction
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 on wrong events. 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 allocation
Resource loading
Resource leveling using ALAP heuristics
Resource scheduling
Crashing a project
Cost-time trade off
Advantages and disadvantages
Conclusion
Annotated bibliography
References
Cite error: Invalid parameter in <ref> tag