Resource allocation and crashing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 24: | Line 24: | ||
<ref name=''web1''> ''https://link-springer-com.proxy.findit.dtu.dk/content/pdf/10.1007%2F3-540-27852-4.pdf'' </ref> | <ref name=''web1''> ''https://link-springer-com.proxy.findit.dtu.dk/content/pdf/10.1007%2F3-540-27852-4.pdf'' </ref> | ||
<ref name=''Slides1''> ''dr. ir. Broekmeulen. Rob "Slides from Project Management"'' </ref> | <ref name=''Slides1''> ''dr. ir. Broekmeulen. Rob "Slides from Project Management"'' </ref> | ||
<references /> | <references /> | ||
Revision as of 16:30, 18 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,
Resource allocation
Resource loading
Resource leveling using ALAP heuristics
Resource scheduling
Crashing a project
Cost-time trade off
Advantages and disadvantages
Conclusion
Annotated bibliography
Fast tracked project Calculate
References
- ↑ Meredith, Jack and Mantel, Samuel (2009) "Project management a managerial approach 7th Edition
- ↑ https://link-springer-com.proxy.findit.dtu.dk/content/pdf/10.1007%2F3-540-27852-4.pdf
- ↑ dr. ir. Broekmeulen. Rob "Slides from Project Management"