Resource Management Smoothing and Levelling
In the Open Standard
James QuirkMember for 17 years 10 months
- Created
- 3
- 4
0
Can anyone confirm my understanding of the resource management process?
My view is that if you can not increase the level of resource/extend working hours or split tasks... you should always try and smooth your programme (i.e keep your end date through using all available float) however, if resource constraints remain then you level the programme which will give you more time to complete the tasks.
I have a fiver riding on this so any help would be apprciated
Thanks in advance
My view is that if you can not increase the level of resource/extend working hours or split tasks... you should always try and smooth your programme (i.e keep your end date through using all available float) however, if resource constraints remain then you level the programme which will give you more time to complete the tasks.
I have a fiver riding on this so any help would be apprciated
Thanks in advance
3 replies
Oldest first- 0Omar Grant ·Hi James - as a person who has never trusted software resource levelling algorithms my methos is to set up the gantt chart with the resource histo’s below and the free float column open. I then move tasks around within their free float to try to level out any peaks; moving within total float I am very wary of as it applies to a path of activities. To be honest, in my experience, if there is no easy solution to getting rid of massive peaks because of minimum float available then it points to too tight a schedule anyway,
cheers,
Omar
Log in or join to reply
ProjectControls.com is free to join. Members can post questions, reply, vote and follow discussions.
Existing members: your original username and password still work. Forgot password?