Project_Managers_should_use_their_budgets_to_bid_for_resources
| Hometown: | Melbourne, Australia |
| Specializations: | Java, Ruby on Rails |
| University: | Software Engineering & Economics, Melbourne University |
| High School: | VCE, Melbourne High School |
| Links: |
|
One of my colleagues currently finds himself torn between two projects. The one he is currently working on and the one he is supposed to be starting next week. Problem is that lack of resources have meant that both projects need him at the same time...
We came up with what we thought was a 'unique' way of addressing this. Developers should be put up for auction for projects within an organization 
Each PM has a set budget for each project, and uses that budget to bid for their desired developer accordingly. Obviously, the projects with the bigger budgets can afford to purchase more developers for greater periods of time. Projects with lesser budgets can still get developers but just fewer of them for fewer amounts of time. The budget on the project is obviously relative to the projects importance and scale within the organization.
This would follow the same model that many sporting clubs follow when bidding for players, and would solve any arguments about resourcing! If you don't have the cash, or are unwilling to put it up, then you don't get the developers you want!
Market forces at play! hahaha...
Obviously there are probably still some kinks that need to be ironed out before this actually gets applied to a real project 
Comments ...
wash...
to pick me!
5 resources!
comments section of someone else's blog.
I'm wondering what the value really is in bringing in short term contractors to
work on projects. They will always walk out with all the knowledge of the
application they have developed, with only a small amount documented or passed
to the permanents via a handover.
bringing in external contractors is inline with 'agile' methodology.. my
respond to that...'huh??'
"Agile" into the project, regardless of what the true approach will
be...
means to us at XXX"....
"..
....
by using external resource whenever we can
...
..."
huh?? hmmmm... there's a bit of voodoo there.
How does that inline with 'saving some $$'
1. External resource is going to be more costly than recruiting permanent
2. Knowledge thats lost cant be measured by $$
voodoo...
That's exactly the issue. Because there is no direct bottom-line value for
knowledge its easy to dismiss its value compared to the perceived value in
using a short-term contractor over a permanent employee that has to keep
getting paid, even when there is no work for them.
phantom penguin....... where are juuuuuuu
allow comments to be made in their blogs - even if the comments are made by
idiots.
And there is no P in Hamster!
not to do that?