Resource allocation and crashing
From apppm
(Difference between revisions)
| Line 1: | Line 1: | ||
Contents | Contents | ||
| − | + | ||
| − | = | + | = Introduction = |
| + | = Resource allocation = | ||
| + | = Techniques = | ||
| + | = Crashing = | ||
| + | = Introduction = | ||
| + | = Conclusion = | ||
| + | = Annotated bibliography = | ||
| + | = Introduction References = | ||
Abstract | Abstract | ||
Revision as of 12:50, 17 February 2019
Contents
Contents |
Introduction
Resource allocation
Techniques
Crashing
Introduction
Conclusion
Annotated bibliography
Introduction References
Abstract
Becoming a use3
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 loading
Resource leveling using ALAP heuristic
Resource scheduling
Cost-time trade off
Crashing
Advantages and disadvantages
Crash example
